LewisCooper
New member
- Local time
- Today, 08:25
- Joined
- Jan 15, 2015
- Messages
- 2
We have a very mature (over 10 years old) MS Access application that is linked via an ODBC connection to a SQL backend. We deploy the application using RDP on a Terminal Server. Each user has their own copy of the front end application. We are running a full version of Access 2003 not a runtime version.
We have started receiving this error a couple weeks ago, about 1-1-15 . “Cannot update. Database or object is read only.
The VBA code had not changed.
The SQL server had not changed.
Nothing was changed intentionally.
I am willing to $1,000 to the person who can resolve this issue.
We have two veteran Access programmers who, one wrote the code years ago, and have stepped through the code and cannot resolve the issue.
We contracted a SQL expert and his opinion was it was not anything to do with the SQL database.
The code will run successfully IF we run directly against the mdb, however if we attempt to run the code the way it has run for years, via a menu system access application we get the error.
This is the only module/access date out of about 40 in our collection that is having any issues, and it is just one routine with this database that is having issues.
Please contact me direct at 435-657-5467 if you would like to have a crack at it.
Keep in mind we have been developing this Access application for over 15 years and have NEVER been stumped before.
Sincerely
Lewis Cooper
BMS Solutions
Terminal Server OS = 2008 R2 Enterprise
SQL Server OS = Windows Server 2012 standard
SQL server = SQL Server 2008 R2
MS Access Version = MS Access 2003 (11.8321.8405) SP3
We have started receiving this error a couple weeks ago, about 1-1-15 . “Cannot update. Database or object is read only.
The VBA code had not changed.
The SQL server had not changed.
Nothing was changed intentionally.
I am willing to $1,000 to the person who can resolve this issue.
We have two veteran Access programmers who, one wrote the code years ago, and have stepped through the code and cannot resolve the issue.
We contracted a SQL expert and his opinion was it was not anything to do with the SQL database.
The code will run successfully IF we run directly against the mdb, however if we attempt to run the code the way it has run for years, via a menu system access application we get the error.
This is the only module/access date out of about 40 in our collection that is having any issues, and it is just one routine with this database that is having issues.
Please contact me direct at 435-657-5467 if you would like to have a crack at it.
Keep in mind we have been developing this Access application for over 15 years and have NEVER been stumped before.
Sincerely
Lewis Cooper
BMS Solutions
Terminal Server OS = 2008 R2 Enterprise
SQL Server OS = Windows Server 2012 standard
SQL server = SQL Server 2008 R2
MS Access Version = MS Access 2003 (11.8321.8405) SP3