Hello Bart, I'm Henry. I’d like to share some thoughts on your issue. While I’m unable to reply in your native language, I’ve translated the content to better understand your situation.
From your description, the ODBC connection disappears or fails after a reboot, is a common problem. It is caused by the connection being configured in a way that is dependent on a user's session.
The solution is to re-create the connection as a System DSN using a UNC network path.
- User DSN vs. System DSN: You likely created a "User DSN," which is only available when you are logged in. A "System DSN" is available to all users and, more importantly, to system services that may need the connection before you log in.
- Mapped Drive vs. UNC Path: You may have used a mapped drive letter (e.g., Z:\folder\database) in your connection. These drive letters are not always reconnected until after a user logs in. Using the full network path (a UNC path, like \servername\share\folder\database) ensures the connection can always be found.
How to Fix the Issue
- Open the ODBC Data Source Administrator by searching for odbcad32.exe in the Start Menu and running it.
- Go to the "User DSN" tab and delete your existing connection.
- Go to the "System DSN" tab.
- Click "Add..." to create a new connection.
- Configure your connection again. When asked for the database location or file, make sure to use the full UNC network path (e.g., \servername\share\file) instead of a drive letter.
Hope this clears things up! If you find this guidance helpful, you're welcome to click 'Accept Answer'—it helps others find useful solutions too.