Hi, > The application is actually supposed to run on a network and all copies will > access the database file at some central location. I'm currently playing > around with SQLITE_BUSY and SQLITE_LOCKED values and they work 90% of the > time, but then sometimes they don't work for some reason and I get thrown > out of the program. > > This whole networking concept is proving to be a real pain to implement, but > I really need it, so I'll keep banging my head against it :-)
Maybe you should consider writing a SQLite server application that runs on the machine where you store the database file and a client library that does not directly use the file but connects the server for queries. Then you don't have do worry about network file system issues... I think such solutions already exist (SQL relay or so shall be one of them). It would be great if such a client library would be API compatible to the SQLite library itself. Then you could turn a simple SQLite application to a client application for your SQLite server simply by linking against your client library instead of linking with SQLite directly... Just an idea... - Danny -- Danny Reinhold Reinhold Software & Services --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
