Corruption

[Guest]

Will network latency cause corruption to Access 97 databases?

Environment -
Windows 2000 server containing Access 97 database that passes data onto an
AS/400 (Host)
XP Pro workstations with Access 2000 installed but not used.

Process for each transaction -
customer info sent to the host from the workstation, passes through the db
on the server, hits the AS/400 which returns info back to the workstation.

 

['69 Camaro]

Hi.

Will network latency cause corruption to Access 97 databases?

No. Corruption is generally caused by faulty network hardware which
interrupts network connections to the Access database or, . . .

Environment -
Windows 2000 server containing Access 97 database that passes data onto an
AS/400 (Host)
XP Pro workstations with Access 2000 installed but not used.

.. . . as you've discovered, multiple concurrent users opening the same
database file from across the network. To avoid this potential corruption,
most experienced developers split the Access database into a front end and
back end. The back end should contain the tables and relationships and
should be located on the network shared directory. The front end should
contain the database objects (forms, queries, modules, et cetera) and the
links to the tables in the back end. A copy of the front end should be
placed on the workstation of each database user.

And yes, one can have an Access 2000 database front end linking to tables
stored in an Access 97 back end, though it's best to have all computers
using the same version and service pack levels for Access, Jet, and MDAC.

For more information on split databases, please see the following Web page:

http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

 

[Lynn Trapp]

Will network latency cause corruption to Access 97 databases?
Most definitely, especially if it interrupts a write operation. Check the
following website.

www.granite.ab.ca/access/corruptmdbs.htm

 

['69 Camaro]

Hi, Lynn.

I think you and I are using two different definitions of "network latency"
when answering this question. For network latency, I'm using the
definition, "the period of time for the information packet to traverse the
network from the origin to the destination," or network "delay." Modern
computer networking equipment and software protect packets from being
completely dropped, due to heavy network load, collisions, low bandwidth, et
cetera.

It may take a while to get there, but the packets _do_ get there using the
network layer and are reassembled using the network's transport layer. In
this sense, the network latency wouldn't specifically interrupt Jet's data
write to disk operation, but malfunctioning network equipment or software
certainly could.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

 

[Lynn Trapp]

Gunny,
I suspect you are right then. I'm wondering now, what the OP meant when he
said "latency".

 

[Guest]

I am referring to the speed of the network running over a 384 circuit with
heavy usage and not failing equipment.

 

[Tony Toews]

No. Corruption is generally caused by faulty network hardware which
interrupts network connections to the Access database or, . . .

There can be many software problems though such as the infamous
OpLocks or different versions of Jet installed on client workstations.

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

 

[Tony Toews]

Will network latency cause corruption to Access 97 databases?

Environment -
Windows 2000 server containing Access 97 database that passes data onto an
AS/400 (Host)
XP Pro workstations with Access 2000 installed but not used.

Process for each transaction -
customer info sent to the host from the workstation, passes through the db
on the server, hits the AS/400 which returns info back to the workstation.

How is the data sent to the AS/400 host? ODBC?

Are you sharing the FE MDB? How can the workstations not use Access
when hitting the A97 MDB on the 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

 

[Lynn Trapp]

Thanks,
I still recommend you take a look at Tony Toews site to several possible
causes of corruption.