D
doodle
Greetings all.
Windws xp, Access 97.
I am running a split db with multiple users in regional offices. The
connection between servers is too slow for the other offices. So I have
a batch file that runs every night to copy the tables and front end
over to their servers. (The other offices are all Read Only anyway.)
All is well with the batch file. The problem is the linked tables. For
example, for Chicago:
1. I copy the front end database file to a folder on my server named
"Chicago".
2. I open the front end and use the linked table manager to redirect
the links to their server.
-This is very time consuming considering that I have to do this for
every table and for ten different offices.
-After I have made the updates to the table links, I run my batch file
which copies all of the copies over to all of the other servers.
There has to be a better way to redirect the table links.
help.
-doodle
Windws xp, Access 97.
I am running a split db with multiple users in regional offices. The
connection between servers is too slow for the other offices. So I have
a batch file that runs every night to copy the tables and front end
over to their servers. (The other offices are all Read Only anyway.)
All is well with the batch file. The problem is the linked tables. For
example, for Chicago:
1. I copy the front end database file to a folder on my server named
"Chicago".
2. I open the front end and use the linked table manager to redirect
the links to their server.
-This is very time consuming considering that I have to do this for
every table and for ten different offices.
-After I have made the updates to the table links, I run my batch file
which copies all of the copies over to all of the other servers.
There has to be a better way to redirect the table links.
help.
-doodle