I have written two applications which are written in MS Access 97; both of which have full security using different systemdb files.
In order to open the second database it is necessary to stipulate the name and location of the workgroup (systemdb) file that is used with that database, eg
DBEngine.SystemDB = "\full path\xx.mdw"
A new workspace is then created giving the user ID and password, eg
set ws = db.createworkspace("New", "Me", "MyPassword",dbUseJet)
So far so good, but the routine fails as the new workgroup file is ignored.
Using "? DBEngine.SystemDB" in the Immediate window replies with the name of the workgroup file used when the current database was opened, where in fact it should display the new workgroup file "xx.mdw".
All the documentation I have read gives similar examples and all fail to work. This is not confined to a single computer.
In order to open the second database it is necessary to stipulate the name and location of the workgroup (systemdb) file that is used with that database, eg
DBEngine.SystemDB = "\full path\xx.mdw"
A new workspace is then created giving the user ID and password, eg
set ws = db.createworkspace("New", "Me", "MyPassword",dbUseJet)
So far so good, but the routine fails as the new workgroup file is ignored.
Using "? DBEngine.SystemDB" in the Immediate window replies with the name of the workgroup file used when the current database was opened, where in fact it should display the new workgroup file "xx.mdw".
All the documentation I have read gives similar examples and all fail to work. This is not confined to a single computer.