We have a fairly simple communications server set up here. We recently 
added electronic faxing. We're using a 3rd party component to handle that, 
which saves the faxes it receives to a SqLITE database. To tie it to our 
existing systems, we've hacked up a little synchronizer which scans the 
SqLITE database for changes every couple of minutes, and pulls some records 
across into our existing database.

During normal operations, the SqLITE connection is left open. This works 
fine so long as the scanner is running. The system pauses itself between 
11PM and 7AM. When that happens, the SqLITE connection is closed, and the 
connection object in .net disposed. When the system resumes at 7AM, the 
connection object is re-created. Connection string used is "Data 
Source={0}; Version=3; FailIfMissing=True". The connection creates and 
opens without error, but when we attempt to access the datatable, we get an 
exception: 

>       25/09/2013 09:28:01 :: SQLite error
>       no such table: faxes

Killing the program, then re-opening will let it run correctly for another 
24 hours. The function calls to generate the SqLITE connection on launch 
and on resume are identical - same code is called, same parameters passed. 
Unsure how to proceed from here - any ideas?

Thanks - 
        Mike
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to