Forum > Databases
cannot load sqlite3.dll
CharlyTango:
@Thaddy You are absolutely right....
... if the goal is one set of compatible dlls per database server and the idea not to pollute the project environment.
And that you are confident that the future target environment in which the programme will run is installed correctly and that there are no side effects to already installed libraries and applications.
I prefer not to pollute the operating system, especially that of the customer. That's why my programmes come with all the necessary dlls in their own directories.
Of course, installation programmes could solve some of the problems mentioned, but not all of them.
In companies with centralised rights and installation management, things may look different, but for me, this strategy causes fewer problems, but of course everyone should do as they wish
Thaddy:
--- Quote from: CharlyTango on July 23, 2024, 09:50:53 am ---In companies with centralised rights and installation management, things may look different, but for me, this strategy causes fewer problems, but of course everyone should do as they wish
--- End quote ---
During development, feel free to do what you like, but on deployment, do not forget "the prodigal son of software engineering":
Write a proper installer... ;D
Actually it is usually the software engineer who is the sinner, not the deployer...
steveinalabama:
I no longer get the sqlite3.dll error, but I still get "cannot find the file listed sqlite3connection1"... I assume that is the file that the connection points to. It is showing the component name. but the database file name is there.
dsiders:
--- Quote from: steveinalabama on July 23, 2024, 08:43:39 pm ---I no longer get the sqlite3.dll error, but I still get "cannot find the file listed sqlite3connection1"... I assume that is the file that the connection points to. It is showing the component name. but the database file name is there.
--- End quote ---
Then you are probably using a relative path to the db file and it is not valid when the application is run. Use a a fully-qualified path in filename or make the path relative to the directory where the application executable lives. IOW, the difference between the current directory at design-time and run-time. Use FileExists() to check for the db file before opening.
HTH...
steveinalabama:
both problems have cleared up, but now a new problem. The sqlite3connection does connect, but when I pen the query I get the error "database not assigned".
The only choices in the database oroperty on the sqlquery are "Sqlite3 connection" or "None". I tried selecting none and then typing in the path and database file name, but it would not allow it with invalid property vale when I try to move back to the form.
In the debugger I see that the connection gets connected, but the error comes when I open the query.
Any ideas?
Navigation
[0] Message Index
[#] Next page
[*] Previous page