By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
462,257 Members | 516 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 462,257 IT Pros & Developers. It's quick & easy.

Why would database in Access Runtime point to incorrect directory?

P: n/a
I have created a database on my computer which has the full application of Access 2007. The users I want to have access will be using Access runtime 2007.

I have split the database and copied both frontend and backend files to the shared drive but, the frontend file keeps pointing back to the original location the database was created in when viewed in runtime. When I go to view it on the shared drive it appears at location of the shared drive. How can I redirect the path for the file in the shared drive so I can view the information in runtime?
Oct 6 '10 #1
Share this Question
Share on Google+
5 Replies

P: 393
Sounds like you split the DB prior to moving it to the shared drive. You'll have to redirect the front end(s) to the shared drive.

Open the front end
Right click on any linked table
Select the 'Linked table manager' option (or something of that sort)
Remap to the shared drive
Oct 6 '10 #2

P: n/a
I did split the database before placing it on the shared drive. I attempted to link the tables and remap as you suggested but, I am still getting the same message. Would I be able to bring the database back together then re-split on the share drive? Help... I am no expert by any means but, I am trying my best to make this work.
Oct 6 '10 #3

Expert Mod 10K+
P: 14,534
Can you post the runtime code? You should find it by looking at the properties of the runtime file.
Oct 6 '10 #4

P: n/a
Looking at the msaccess.exe I see normal .exe properties…
Looking at your database files I see normal data file properties…
Because I cannot open the bases, I cannot see any access properties
Oct 11 '10 #5

Expert Mod 10K+
P: 14,534
Normally if you right click on the runtime file and go to properties it will give you code for the running runtime file including path to the backend.
Oct 13 '10 #6

Post your reply

Sign in to post your reply or Sign up for a free account.