L
LarryP
We have several Access 2003 databases that link to numerous source files on a
workgroup server at our main location. Unfortunately, people at some of our
sublocations can't make use of these databases because of bandwidth issues:
although they can "see" the main location server and the relevant files, when
they try to run the databases things get really, REALLY slow. Screens that
display in 10-15 seconds here take 20 minutes there, etc. The IT guys say
not to hold our breath waiting for a hardware fix, it ain't gonna happen any
time soon.
So, we're contemplating copying all the necessary files, currently about 2GB
worth, to a server at the remote location once a week. Doing that, though,
would involve resetting a couple dozen links in the front ends of the various
databases. For obvious reasons we don't want to have to maintain multiple
front end versions, so we're envisioning a procedure in the common front end
that says "If I'm logging on at the home office, set all the links to
xxxxxxx, but if I'm logging on at sublocation A, set the links to yyyyyyyy,
...." etc. The necessary data about what the links should be for each
location would be stored in a table.
Has anybody tried anything like this, and if so, with what result? What
problems might we encounter, and what suggestions might anyone offer to make
the transition to this solution as painless as possible? Just hoping for
general guidance before we put a lot of effort into this.
workgroup server at our main location. Unfortunately, people at some of our
sublocations can't make use of these databases because of bandwidth issues:
although they can "see" the main location server and the relevant files, when
they try to run the databases things get really, REALLY slow. Screens that
display in 10-15 seconds here take 20 minutes there, etc. The IT guys say
not to hold our breath waiting for a hardware fix, it ain't gonna happen any
time soon.
So, we're contemplating copying all the necessary files, currently about 2GB
worth, to a server at the remote location once a week. Doing that, though,
would involve resetting a couple dozen links in the front ends of the various
databases. For obvious reasons we don't want to have to maintain multiple
front end versions, so we're envisioning a procedure in the common front end
that says "If I'm logging on at the home office, set all the links to
xxxxxxx, but if I'm logging on at sublocation A, set the links to yyyyyyyy,
...." etc. The necessary data about what the links should be for each
location would be stored in a table.
Has anybody tried anything like this, and if so, with what result? What
problems might we encounter, and what suggestions might anyone offer to make
the transition to this solution as painless as possible? Just hoping for
general guidance before we put a lot of effort into this.