D
dorenstein
For years I have been maintaining a 2000 database then
converting it to a 97 database, which requires a minor code
change. I have a number of applications that access the
database in an unsecured way. (They create a DSN on the
fly with no "system database".) The conversion warns that
security settings are lost, but this has never been an issue.
Suddenly, none of the applications can access any tables;
they get read permission errors. Our IT dept. has pushed a
lot of patches to our Windows 2000 machines lately, but
even on an old NT machine, I see the same behavior.
Manually setting all user group permissions does nothing.
Any ideas?
Please send them to (e-mail address removed). Thanks. P.S.
The 2000 database works fine.
converting it to a 97 database, which requires a minor code
change. I have a number of applications that access the
database in an unsecured way. (They create a DSN on the
fly with no "system database".) The conversion warns that
security settings are lost, but this has never been an issue.
Suddenly, none of the applications can access any tables;
they get read permission errors. Our IT dept. has pushed a
lot of patches to our Windows 2000 machines lately, but
even on an old NT machine, I see the same behavior.
Manually setting all user group permissions does nothing.
Any ideas?
Please send them to (e-mail address removed). Thanks. P.S.
The 2000 database works fine.