moving a split database

  • Thread starter Thread starter Darren
  • Start date Start date
D

Darren

I have a database that has been split. I need to install it on a new machine,
how do I change the original path?
 
Use the Linked Table Manager (Tools menu.)

To design an application for others to use, you want your initialization
procedure to test if the back end is available, and take suitable action if
not. There's an example of how to do that in a module of Microsoft's
Solutions database, downloadable from:
http://support.microsoft.com/kb/248674
 
This DB has alrady been split by another person, the PC that it on is being
replaced and we cant keep the same file structure. so when i place the DB on
the new pc i get an error message saying that the path is not valid.
 
So solution suits you? The Linked Table Manager? Or the code?

Or are you stuck with getting started because you can't get it?
You could try holding down the Shift key when you open the database.
 
Did you try the Linked Table Manager yet?

(Hint: the first reply you received indicated what Menu you should look on
to find it.)
 
Most of my options are greyed out on my menues.

Allen Browne said:
Did you try the Linked Table Manager yet?

(Hint: the first reply you received indicated what Menu you should look on
to find it.)
 
Is that code available on a website anywhere?
We are not allowed to download anything from the internet.
 
mscertified said:
Is that code available on a website anywhere?
We are not allowed to download anything from the internet.

That's a ridiculous restriction. Time to change jobs.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Tony Toews said:
That's a ridiculous restriction. Time to change jobs.

You'd be surprised just how many places of work have that restriction in
place, my own included.

Keith.
 
The basic reconnect code is here:
http://allenbrowne.com/ser-13.html

That particular example assumes the back end and front end are in
the same folder. The solutions.mdb code pops up a dialog asking
the user to locate the file, and then uses that path. The FileOpen
code is here:
http://www.mvps.org/access/api/api0001.htm

There's also a couple more examples here:
http://www.mvps.org/access/tables/tbl0009.htm
and for ODBC tables:
http://www.mvps.org/access/tables/tbl0010.htm

For easily reconnecting to multiple back ends:

http://www.dfenton.com/DFA/download/Access/Reconnect.html

That has skeleton code for dealing with ISAM tablelinks and ODBC,
but only the Jet linked tables actually work. I've never gotten
around to dealing with the other two.
 
Keith Wilby said:
You'd be surprised just how many places of work have that restriction in
place, my own included.

However many code samples are included in MDBs. If you copy and paste
out of those MDBs what's the harm?

I can understand not installing software but in corp/govt environments
users are administrators of thier systems anyhow.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Back
Top