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

Lost back end connection

P: n/a
I have a split database (A2K). The back end was originaly on drive J.
IT changed some network stuff and eliminated the J drive. The back end
is now on the F drive. When the front end is opened, it looks for the
back end on the J drive and displays a message saying the filepath of
the back end is not a valid path.

Is there any way to reconnect the front end to the back end?

The front end appears to open. An Access.LockFile is created, but
nothing appears on screen. Not even the database window. The Linked
Table Manager is not available, neither is Get External Data. I can't
see any way of changing the location of the back end.

Any suggestions are greatly appreciated.

Randy

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"RBohannon" <ra*****@hotmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...
I have a split database (A2K). The back end was originaly on drive J.
IT changed some network stuff and eliminated the J drive. The back end
is now on the F drive. When the front end is opened, it looks for the
back end on the J drive and displays a message saying the filepath of
the back end is not a valid path.

Is there any way to reconnect the front end to the back end?

The front end appears to open. An Access.LockFile is created, but
nothing appears on screen. Not even the database window. The Linked
Table Manager is not available, neither is Get External Data. I can't
see any way of changing the location of the back end.

Any suggestions are greatly appreciated.

Randy


Try holding down the shift key when you open the application.
--
Randy Harris
(tech at promail dot com)
Nov 13 '05 #2

P: n/a
Thank you! This allowed me to open the Linked Table Manager and set
the links to the proper tables. There is still something hinkey with
the app. I keep getting error messages that say Access could not
"read" some instruction at some location.

However, I have been able to reconstruct the entire DB from parts that
were recoverable, and it was easier than I anticipated it would be.

Thanks for the help.

Randy

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.