networking & remote connections

[Guest]

Here is the scoop. We use Access 2000 and 2003. The databases were created
in 2000. We have Site 1 which houses database A and database B on it's
server. Database B reads from database A (linked tables). When sitting at
Site 1 no problems. When sitting at Site 2, which has a mapped drive to Site
1's server, I try to open up database B. It has take over an hour at times
to open this database. There have been a few occasions that I have opened
database B in two minutes, however when I try to retrieve a record or report
I could literally be sitting here all day looking at an hour glass waiting
for database B to retrieve the info from database A.

From what I understand about splitting you have to be using the same version
of Access, so that's not going to happen anytime soon. So that doesn't seem
to be an option for me.

What can I try?

 

[Pieter Wijnen]

check at http://allenbrowne.com


--
Pieter Wijnen

My feeble Access pages (good links though)
http://www.thuleeng.com/access
When all else fail try:
http://www.mvps.org/access
http://www.granite.ab.ca/
http://allenbrowne.com/
http://www.lebans.com/

 

[Tony Toews]

Here is the scoop. We use Access 2000 and 2003. The databases were created
in 2000. We have Site 1 which houses database A and database B on it's
server. Database B reads from database A (linked tables). When sitting at
Site 1 no problems. When sitting at Site 2, which has a mapped drive to Site
1's server, I try to open up database B. It has take over an hour at times
to open this database. There have been a few occasions that I have opened
database B in two minutes, however when I try to retrieve a record or report
I could literally be sitting here all day looking at an hour glass waiting
for database B to retrieve the info from database A.

What kind of connection from Site 1 to Site 2? ADSL? T1? Anything
under 10 mpbs second is too slow for Access and even 10 mpbs on a WAN
is very questionable.

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

 

[Albert D. Kallal]

Actually, splitting allows you to run a mixed environment.

That means you could have a97, a2000, and a2003 uses ALL WORKING on the SAME
back end data file.

The simply solution is to split, and then distribute a front end version to
each user (a97 users would get a a97 version, a2000, would get a a2000
version). This would mean that you back end data must be kept in the LOWEST
common format that you plan to use.

so, if you plan to have a2000, and a2003 users at the same time, then the
back end data file would be in a2000 format...

So, read the following article on splitting. It will thus solve your problem
of different versions hitting the back end data..

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

It has take over an hour at times
to open this database.

Logic would dictate that your connection is slow. Did bother to even check
the speed?

I talk about using a wan here:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

The wan article will likey solve your speed problem for the other "remote"
building/users.

 

[Guest]

I really appreciate your help and I think with the articles youv'e suggested
that I read, I found a solution.

1. Splitting the database didn't work. When I starting looking at what
splitting does the two databases esentially already are split. DB 1 contains
most of the data. DB 2 links the tables from DB 1. DB 2 has 3 tables that are
housed in DB 2, the rest are linked from DB 1. I did do the split and put
the front end on my pc and the be on the remote server... same results as
before the split.

2. You would think that logically it would be because the network is slow,
however... DB 1 is 5meg DB 2 is 2Meg. Opening up DB 2 is what is taking
the hour to open, it contains the links back to DB 1 tables. DB 1 takes two
minutes to open. If it were a connection speed problem wouldn't DB 1 that is
larger take longer to open? To me it seems to have more to do with the fact
the DB 2 links tables from DB 1. I've also asked our IS&T group what the
connection speed is between the two sites, they haven't gotten back to me yet.

3. The last article that you refered to concerning the WAN is what helped.
I think creating a replica is what is going to work for me. I'm testing it
now and it seems to work well. I'll just have to remember after making
changes to sync them up. I didn't find an option to automate this sync.

Thanks for ALL of your help. If you got anymore ideas let me know.
Denise