Problem with disconnecting

[OliP]

Hello,

I have an application and BD.mdb (Access97) on the server (Windows2003 EE)
with fifteen workstations (Win2k & WinXP), which run the application by
mapping the share on the server. The problem is that after some user run
the application and after doing some job, they don't close the
application, but after some time another user can't run it, because of the
BD is in suspect mode (information from LDBview).

My question is: what is the reason of this? Corrupted NIC, LAN? Maybe bad
settings in ODBC, Registry etc.?

Please, help...

Thanks for all,

OliP

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds like you don't have a front-end/back-end set up. When more than
one user is using an Access db the data tables (back-end, aka BE) must
be separated from the front-end (aka FE: queries, forms, reports,
modules) and each user have a copy of the FE on their PC. This avoids
corruption of the db.

Read the Access Help articles on splitting the db. The Help Contents
hierarchy is:

Working with Data
Sharing Data
Split an Access database

There is a wizard (Access 2002) under

Tools > Database Utilities > Database Spliter

that will walk you thru the process.

Once the db is split & the FE is on each users PC you will have to re
link the tables to the BE. On each PC use

Tools > Database Utilities > Linked Table Manager

for this.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQlrYCYechKqOuFEgEQLZOwCg9Xo8Ow1JMntb8CzmXfVmGJ EpBBIAniwE
itv6yxL301J303qcU2CyhDL/
=aiEz
-----END PGP SIGNATURE-----
OliP wrote:

Hello,

I have an application and BD.mdb (Access97) on the server (Windows2003
EE) with fifteen workstations (Win2k & WinXP), which run the application
by mapping the share on the server. The problem is that after some user
run the application and after doing some job, they don't close the
application, but after some time another user can't run it, because of
the BD is in suspect mode (information from LDBview).

My question is: what is the reason of this? Corrupted NIC, LAN? Maybe
bad settings in ODBC, Registry etc.?