Hi all,
Believe it or not, the organization that I work for is allowing and even specifying different drive letter mappings for individual shared drives.
This I am addressing, but the size of the organization makes changing things very slow, and the MS Access application that I'm developing is currently in use.
My problem is that the app. has links to external databases, and Access seems to store the path with the drive letter. So user a) may have TableA linked via P:/thisfolder/thatfolder/db.table, and user b) needs N:/thisfolder/thatfolder/db.table (to the same table in the same folder in the same database).
I can acquire the current users app. path via CurrentDB(), and relink the tables at runtime, but I'm not sure if this will affect users currently logged-in to the app.
For e.g. user a) opens the app, and a linked table is mapped to P:/thisfolder/thatfolder/db.table, user b) opens the app, and his/her 'instance' of the app. deletes the link and remaps it to N:/thisfolder/thatfolder/db.table.
Will this affect user a) at all, or is the second users copy of the app. really a second instance of the app?
If this will affect user a); is there some way to convert the path returned by CurrentDB to UNC? I don't want to have to specify literal UNC paths if at all avoidable.
Any help much appreciated.
Regards,
Darrylle
Never argue with an idiot, he'll bring you down to his level - then beat you with experience.
Believe it or not, the organization that I work for is allowing and even specifying different drive letter mappings for individual shared drives.
This I am addressing, but the size of the organization makes changing things very slow, and the MS Access application that I'm developing is currently in use.
My problem is that the app. has links to external databases, and Access seems to store the path with the drive letter. So user a) may have TableA linked via P:/thisfolder/thatfolder/db.table, and user b) needs N:/thisfolder/thatfolder/db.table (to the same table in the same folder in the same database).
I can acquire the current users app. path via CurrentDB(), and relink the tables at runtime, but I'm not sure if this will affect users currently logged-in to the app.
For e.g. user a) opens the app, and a linked table is mapped to P:/thisfolder/thatfolder/db.table, user b) opens the app, and his/her 'instance' of the app. deletes the link and remaps it to N:/thisfolder/thatfolder/db.table.
Will this affect user a) at all, or is the second users copy of the app. really a second instance of the app?
If this will affect user a); is there some way to convert the path returned by CurrentDB to UNC? I don't want to have to specify literal UNC paths if at all avoidable.
Any help much appreciated.
Regards,
Darrylle
Never argue with an idiot, he'll bring you down to his level - then beat you with experience.