Hi,
I am trying to improve speed in a VB client application for a WAN (am I a hero or what ?!)
There are some reports generated by copying data from the database to a temporary database and then displaying the report.
The copy is made using Update function. Both recordsets (actual source and temporary destination) are Dynasets.
Sometimes the copying is done in good conditions, with no network activity (except the initial SELECT).
Some other times, while executing Update, VB starts talking some nonsensish to the main database, telling it to go in and out of autocommit mode. Excerpt of SQL log:
"odias fffbd721:fff9793d ENTER SQLSetConnectOption
HDBC 0x0615fcfc
UWORD 102 <SQL_AUTOCOMMIT>
UDWORD 0
Modias fffbd721:fff9793d EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0x0615fcfc
UWORD 102 <SQL_AUTOCOMMIT>
UDWORD 0
Modias fffbd721:fff9793d ENTER SQLTransact
HENV 0x0615fc5c
HDBC 0x0615fcfc
UWORD 0 <SQL_COMMIT>
Modias fffbd721:fff9793d EXIT SQLTransact with return code 0 (SQL_SUCCESS)
HENV 0x0615fc5c
HDBC 0x0615fcfc
UWORD 0 <SQL_COMMIT>
Modias fffbd721:fff9793d ENTER SQLSetConnectOption
HDBC 0x0615fcfc
UWORD 102 <SQL_AUTOCOMMIT>
UDWORD 1
Modias fffbd721:fff9793d EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0x0615fcfc
UWORD 102 <SQL_AUTOCOMMIT>
UDWORD 1"
This is _very_ bad for performance in a WAN where any ODBC command has a high price (latency _and_ bandwidth problems).
Please help me. Thx.
Cristi
