PeterWieland
Registered User.
- Local time
- Today, 13:33
- Joined
- Sep 20, 2000
- Messages
- 74
Hi,
I have a A2000 frontend, SQL2000 backend database, and I have used the code from Microsoft Knowledge Base to Relink ODBC tables when the database opens. This logs the user into the SQL server tables as a data browser user, the username and password stored in a table as per the MS article. I have created a second, similar procedure and table that should log the user in as the dbo for admin purposes. This code is run from a password protected command button. Most of the time the tables relink ok, with full rights, but sometimes 1 or 2 of them only have the original read permissions, and records cannot be added/deleted/modified. If I goto Tools/Database Utilities/Linked Table Manager and manually relink the table all is ok.
Does anyone know why this happens, and more importantly, how to stop it?
Peter
I have a A2000 frontend, SQL2000 backend database, and I have used the code from Microsoft Knowledge Base to Relink ODBC tables when the database opens. This logs the user into the SQL server tables as a data browser user, the username and password stored in a table as per the MS article. I have created a second, similar procedure and table that should log the user in as the dbo for admin purposes. This code is run from a password protected command button. Most of the time the tables relink ok, with full rights, but sometimes 1 or 2 of them only have the original read permissions, and records cannot be added/deleted/modified. If I goto Tools/Database Utilities/Linked Table Manager and manually relink the table all is ok.
Does anyone know why this happens, and more importantly, how to stop it?
Peter