Hi There,
I have a user -level secured Access 97 database, which has to stay in Access 97 because most of my users are still in Access 97. However, I do have few who use Access 2000. I've got shortcuts, bat files, etc working to where their Access 2000 program goes through the correct workgoup file and finds the database, no problem (The secured database is on a shared remote drive) and the DAO compatability and all that has already been addressed and works ok, however, this is the problem--
Once the Access 2000 users are logged in with their respective user level permissions, they of course receive the perfectly logical and expected error message, "The current user does not have permission to convert or enable this database." Because, as I know, whenever I as the admin open 97 with 2000, it gives me the choice of either converting or opening the db, and in this case it will only give me the choice if 1) I am logged in as admin, and 2) I open the database exclusively "the first time" ("the first time" I guess means only for that network session (?), because the next day when I log back onto the network it says I have to open it exclusively "the first time" again, even though that is not the first time I have logged on from that computer as a 2000 user, and anyway, with a multi-user database, obviously one can't be in exclusive mode alot of the time, much less have permissions to do so (and thus be granted a choice to open or convert)if they are not the admin....)
My point/problem is , I really believe that there should be an easier way for an Access 2000 user to participate in a shared and secured Access 97 database, but it seems as if their permissions are always going to prevent them from even opening it on a consistent basis without major problems and hangups...
Has anyone else had this sort of problem, and if so, did they find a solution?
Thanks
I have a user -level secured Access 97 database, which has to stay in Access 97 because most of my users are still in Access 97. However, I do have few who use Access 2000. I've got shortcuts, bat files, etc working to where their Access 2000 program goes through the correct workgoup file and finds the database, no problem (The secured database is on a shared remote drive) and the DAO compatability and all that has already been addressed and works ok, however, this is the problem--
Once the Access 2000 users are logged in with their respective user level permissions, they of course receive the perfectly logical and expected error message, "The current user does not have permission to convert or enable this database." Because, as I know, whenever I as the admin open 97 with 2000, it gives me the choice of either converting or opening the db, and in this case it will only give me the choice if 1) I am logged in as admin, and 2) I open the database exclusively "the first time" ("the first time" I guess means only for that network session (?), because the next day when I log back onto the network it says I have to open it exclusively "the first time" again, even though that is not the first time I have logged on from that computer as a 2000 user, and anyway, with a multi-user database, obviously one can't be in exclusive mode alot of the time, much less have permissions to do so (and thus be granted a choice to open or convert)if they are not the admin....)
My point/problem is , I really believe that there should be an easier way for an Access 2000 user to participate in a shared and secured Access 97 database, but it seems as if their permissions are always going to prevent them from even opening it on a consistent basis without major problems and hangups...
Has anyone else had this sort of problem, and if so, did they find a solution?
Thanks