Paul Bainter wrote: > > When I run the program on the target machine, the main window comes up fine > because it doesn't access the database, but once I bring up a window that > does access the database, I get a message stating that the application has > stopped working. No error message specific to the problem and then another > window from the OS stating that it will try to discover what the problem is, > but of course it can't. >
Do you have a stack trace showing where the exception is happening? Can you enable just-in-time debugging on one of the deployment machines? Do you know what type of exception is being thrown? I suspect the exception being thrown is due to the native "SQLite.Interop.dll" not being found, being the wrong architecture (x86 versus x64), or missing its runtime libraries. Without the stack trace and/or the type of exception being thrown, it's very hard to be sure which issue you are encountering. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users