Link to home
Start Free TrialLog in
Avatar of teksolgreg
teksolgregFlag for United States of America

asked on

Access 2013 DB Move

Having issue opening database after copying database files and moving to new server.  Upon attempting to open database, error message indicates file cannot be found with old data location in the error.  For example:
Old Data location: \\old_server_name\shared_folder_name\123.mdb
New Data location: \\new_server_name\shared_folder_name\123.mdb

Tried to open two ways:
1. Browsed to new server and location (\\new_server_name\shared_folder_name\123.mdb) and attempting to open file, received error message that old server ( \\old_server_name\shared_folder_name\123.mdb) is not available.
2. Opened Access and browsed to location on new server and received the same message relating to old server location.

Stuck in mud ...
Avatar of teksolgreg
teksolgreg
Flag of United States of America image

ASKER

I should also note, the database is not a sql database.
ASKER CERTIFIED SOLUTION
Avatar of Jeffrey Coachman
Jeffrey Coachman
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Jeffrey,
Thank you so much for the response - I am totally not an Access user, the company I do maintenance for had us install a new server.  Along with that, came moving data.  Now that I've drawn the picture a little clearer on my input.  I can't even open the mdb file due to the error, so using the linked table manager is unclear to me and hence leaving me at a stand still.
I can't even open the mdb file due to the error,
Can't open the front end?, ...or can't open the back end?
...or neither?
Not to backtrack too much, but, we have a db file that when chosen on the old server, a user interface would open in Access.  There are several files in and around that file in that location, but, I couldn't tell you the front end from the back end or how to manipulate either of them being all I get is error messages when trying to open any of the db files that used to open on the old server.
I suspect from your comments, that this is a split db and the file I am clicking on is the front end and the front end is merely asking where is the back end located.  After it is not found, or the location is not found, the error message pops up.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There may be an easier answer.... so lets see what other experts post.

Can you simply put the db back on the old server and open it?
See if you get any errors, ...then try to figure out which are front end and which are back end files...

Also, ...is the original developer still around?
Can you contact them to get info on the database(es)?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Developer long gone, maybe even passed.
Database opens with no issue when our last remaining user, still part of old domain, opens file.  File is opened by opening Access and browsing to the location and no issue or error occurs.
There never was any update to a front end at all, on any desktop, by any user, ever.  Each user had a copy of the latest MS Access installed locally, the database files were always located on a shared drive on the server, were accessible by all users on the domain, at all times.  Granted, there are only three users, but, each user could edit a record, save it and the next user would see the result of the edit.
Now we have a new server and accessing the file in the same manner errors out looking for the old server location.  Based on this, I suspect the FE requires a "re-linking" to the new BE?  This is just a stab in the dark though.
I'll totally try the holding down of the shift key - shoot, at this point, I will press shift with one hand, do a cartwheel on the other and cross my fingers with my toes to get this to work :)
Note that once you bypass the startup stuff (if you can), then you'll still need some basic Access skills in order to troubleshoot this. Like the others, I'd believe a relink is in order, but if the application has hard-coded paths to certain things (and that's not unusual with novice-built systems), you may find yourself in deep waters.
@Scott, I appreciate the comment, but have not been able to bypass anything.
If you can't get to the design mode of the system, you may also find that you're dealing with a .mde/.accde format. Those formats don't allow design changes, although you can relink (assuming you can get to the point where you relink).

You can always do it via code, of course, but you'd have to write the code to do it. That's assuming the relink is your trouble, obviously.

At some point you might consider hiring this out to an Access dev to manage.
We have a free J Street Access Relinker, but as Scott says you need to be able to get into the code in order to incorporate it.  I agree that if you're having trouble, it might be best to use a consultant to figure this out.

http://www.JStreetTech.com/downloads

Cheers,
Armen Stein, Access MVP
J Street Technology
Checking with one consultant now, they are not very responsive.