Access Crashes on Wireless Network

  • Thread starter Thread starter BobVerhey
  • Start date Start date
B

BobVerhey

An Access XP client app running on Windows 2000 and
accessing Sybase data over a wired network works OK. The
same app on the same laptop routinely crashes when
accessing data using a wireless network. Utilities with
the wireless PCMCIA card shows varying signal strength
and signal quality, but only Access apps crash regularly.
The app doesn't appear to crash in any particular place
more often than any another place.

Assuming there are some network delays in the wireless
environment, are there network or ODBC parameters that
can be tweaked to make Access more forgiving? Or perhaps
you have other thoughts as to why this might be happening?

Any ideas appreciated!
 
Your Sybase data is presented by a service. As a file database, Access is
going to be prone to problems with ANY network issues. Access is notorious
for corrupting files with a bad network. Using Access over wireless is is
asking for trouble.
 
An Access XP client app running on Windows 2000 and
accessing Sybase data over a wired network works OK. The
same app on the same laptop routinely crashes when
accessing data using a wireless network. Utilities with
the wireless PCMCIA card shows varying signal strength
and signal quality, but only Access apps crash regularly.
The app doesn't appear to crash in any particular place
more often than any another place.

Assuming there are some network delays in the wireless
environment, are there network or ODBC parameters that
can be tweaked to make Access more forgiving? Or perhaps
you have other thoughts as to why this might be happening?

Any ideas appreciated!
Click to expand...

Yes, there is an ODBC timeout parameter that you can experiment with.

But, Access is more sensitive to network disconnections than most other
applications, so, as Paul indicated, running it on a wireless network (where
disconnections, intermittent or longer, are more common) isn't the most
"friendly environment for Access".

If "all is well" with the wireless network and you don't experience
disconnections and delays, then it should be fine.

Larry Linson
Microsoft Access MVP
 
Albert D. Kallal said:
You need to use the other database engine included on the office cd with
ms-access if you are going to do this.
Click to expand...

Or use Terminal Server.

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
 
the Jet odbc options are in the registry at
\HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\ODBC

(take a look to see what the options are)

you can also set the values at runtime like this:
Application.dbengine.setoption dao.dbExclusiveAsyncDelay, 5
or this:
Application.dbengine.setoption 60, 5

Also, I would be looking at the ODBC drivers and
wireless drivers to see if they could be optimised
for this application.

Another option might be to bind all your bound forms
to local tables, and use ADO or ODBCdirect to get
and set the data.

same app on the same laptop routinely crashes when
accessing data using a wireless network. Utilities with
Click to expand...

what exactly happens?

(david)

PS: Jet itself is extremely demanding on network quality,
but based on your message, Jet is not using the network
at all: it is communicating with a local ODBC driver, and
the ODBC driver is using the network. ODBC drivers are NOT
supposed to crash just because there are network delays,
and wireless network drivers are supposed to handle all the
error correction.
 
Back
Top