Hi,
I did read the archives, along with information on the web site, and am aware of the risks I take using SQLite in concurrent mode.
Still, since over half of our customers still don't have the Net (hence, usually use NetBeui as their network protocol instead of TCP/IP), and asking them to have someone deploy TCP/IP on their network and run an installer on the server is way too much work for such small installations, so deploying a client/server solution like MySQL is just not good a good idea.
So... we're willing to take the risk of using SQLite in a multiple-host context to share data with among our VB applications on 9x and NT hosts.
=> What are the tricks that we should use to minimize the risk of data corruption?
1. The first user to start working in the morning will trigger the creation of a backup of the DB file, so that we have a valid copy of their data as they were in the morning of that day. We'll find a way to take more snapshots during the day (eg. check for activity on the server or time of day, etc.)
2. Make use of the BUSY error code, wait a second, try again up to X times until giving up when another host has locked the database for write access
3. Using a file on the server as on/off semarphor?
4. Other ideas?
Thank you very much for any tips Fred.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
