Using the VB wrapper dll SQLite3VB.dll from Todd Tanner's site: http://www.tannertech.net/sqlite3vb/index.htm
In one particular procedure I had a serious problem when doing a call to sqlite_get_table, causing Excel to crash. It took me a long time to pinpoint the trouble as VBA debugging methods didn't help here. Eventually it appeared that the trouble was calling sqlite3_close too soon after sqlite_get_table. Not sure if this makes sense, but after moving sqlite3_close some lines down in that procedure the problem seems to be solved, so I take it the connection was closed while SQLite was still fetching data, causing the error and the Excel crash. So what is the best way to determine if sqlite_get_table is finished? Running number_of_rows_from_last_call in a loop might be something, but maybe there is something better. RBS ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
