Back End tables exist on an obsolete server 2

[BoxHead]

Our server crashed and all of the backup files were moved to a new server with a different name. My front end will not open at all. A message appears stating that the path is not valid. Holding shift while opening and F11 are not getting me any further.

Is there a way to change linked tables in the registry or another way to get this nut cracked?

Thanks!

John

 

[Remou]

Have you got the original mdb or an mde?

 

[BoxHead]

When you say original, if you mean the mdb prior to splitting - I do not. I built the db 4 years ago, left the company for a year and came back in a different position. All of the files, folders, and drives with my projects from the first position I held here were 'cleaned up' when I left.

 

[Remou]

I mean not the compiled, mde version. Excuse me for pressing the point, but did you keep the shift key held down until the database was fully opened?

 

[BoxHead]

We're using the database as an MDB - actually 2 MDB's - front end/back end.

I did hold the shift key down for a long time, several times. My startup options were set up to prevent users from doing that.

I'm working on importing everything from the front end into a new DB. It didn't carry over the Startup Options from the original - which is good. I have some query field names to update since I imported them before I linked to the new table locations.

I think this will work, but I'm going to have to do some rethinking on my startup options.

Thanks Remou

 

[Remou]

This might help:

http://www.mvps.org/access/general/gen0040.htm

 

[danvlas]

ftp://ftp.artrom.ro/StartupOptions.zip
You'll be able to 'remotely' reset all of them.




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[BoxHead]

Thanks for the help! You saved me again!