MS Access 97

[Guest]

Hi,

I have users experiencing issues with Access 97 Databases. The file server
is located at Building A and users are spread between Building A and B. Both
buildings are connected via WAN connection. Users are Building B always gets
error when they generate reports to the Excel 97, after that they will not be
able to save the reports onto the file server or on their PC desktop but
users at Building A does not face any issues at all.

Is there a article which mentions that Access 97 and Access 2003 is not WAN
friendly and it takes up a lot of bandwidth? They are looking into upgrading
to Access 2003 which I think they might faced the same problem too. I am
thinking of asking them to use a proper Database solution like SQL but I will
need some facts on it before I can push this forward.

Please advise if anyone can provide the article.

Regards.
Larry

 

[Rick Brandt]

Hi,

I have users experiencing issues with Access 97 Databases. The file
server is located at Building A and users are spread between Building
A and B. Both buildings are connected via WAN connection. Users are
Building B always gets error when they generate reports to the Excel
97, after that they will not be able to save the reports onto the
file server or on their PC desktop but users at Building A does not
face any issues at all.

Is there a article which mentions that Access 97 and Access 2003 is
not WAN friendly and it takes up a lot of bandwidth? They are looking
into upgrading to Access 2003 which I think they might faced the same
problem too. I am thinking of asking them to use a proper Database
solution like SQL but I will need some facts on it before I can push
this forward.

I don't know if you will find an "official" article, but any of the regulars
in these groups will tell you that Access CANNOT be used reliably over a
WAN. The best WAN is still terrible compared to a LAN and Access doesn't
even get along with sub-par LANs.

The usual recommendation is to use remote control software like Terminal
Services, VNC, PC Anywhere, etc., so that all of the Access data and file
traffic stays on the LAN and only the bytes that support the remote control
software pass over the WAN.

 

[Jeff Conrad]

In addition to the information Rick has provided, MVP
Albert Kallal has some thoughts on the subject here:

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

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html

in message:

 

[Albert D.Kallal]

There is two issues with a wan.

1) speed. Most WANS don't have near enough speed (you did not mention this
as a issue, or problem in your post)

2) reliability of connection. Again, you hinted at problems with the
application, and your mentioned problems don't actually have anything to do
with the fact of using a WAN (at least with your information given).

I would first check the users permissions, as this sounds likely your
problem. Remember, when using a jet file share, users need FULL rights to
that shared dir. (again, I am only going to repeat this once: FULL RIGHTS =
delete, create...the whole works).

As mentioned, it is not that ms-access is not WAN friendly, but the wan is
simply not fast enough, nor reliably enough in most cases. If you build a
VERY good and high speed WAN, then a jet file share can, and should
work..but most WANS are not good enough. (again, you made no mention of how
fast, or reliable your WAN is).

Also, you might want to read up on some solutions for using ms-access on a
WAN here:

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

 

[Arvin Meyer]

I am currently running several systems on a WAN without any serious
problems. One system uses a JET database with an ASP front end. Several
others use Access MDB front-ends running on Terminal Servers.

A direct WAN connection, due to the lack of reliability, is a recipe for
corruption. Direct WAN connection eat tons of bandwidth. By contrast both
Terminal Server apps and the ASP app use minute amounts of bandwidth. The
Terminal Servers have never been corrupted, the ASP app has corrupted once,
about 5 years ago when it was first being written. No data was lost. Strong
networks make quality solutions.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access