you and another user are attempting to change the same data at the same time

[nal]

The Microsoft Jet database engine stopped the process because . . .
you and another user are attempting to change the same data at the same
time - 3197

Grr. . .

This error occurs intermittently in 2k and xp - never in 97 - when adding a
new record to a subform. The error msg occurs once for each field in the
subform record which then displays #error. Occurs on networks and
stand-alones, cannot be reproduced at will - you never know when it is going
to happen - and only with a minority of installations.

It looks as if the jet is trying to save the record more than once - any
suggestions would be most appreciated!

nal

[DAWN]

I have seen this issue too; however I have not found the fix yet. I
will post a reply when I have.

Dawn

"nal" <na...@exeter37.freeserve.co.uk> wrote in message news:<9uve53$ok9$1...@news6.svr.pol.co.uk>...

[Allen Browne]

If #Error occurs on each row intermittently and with no
consistency on a networked app, you almost certainly have
a network problem, e.g. bad cable connections, bad card, bad
drivers, excessive traffic, failing server, ...

#Error can also occur if you're attempting to move to another
record (e.g. a new one) when the current record is dirty and
can't be saved.

--
Allen Browne, Microsoft Access MVP
Perth, Western Australia.
Tips for Access users at:
http://users.bigpond.net.au/abrowne1/

[Robert Berman]

Error Number 3197:
Error message:
The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time.
Cause/Problem:

This error typically occurs when a long value column (an OLE or MEMO
data-type) has bad data stored in it. Long value columns are typically
stored in a separate page from the page that the row is stored in. If
a long value column is present in the table schema, the Jet database
engine will attempt to read the long value page when reading the row
of data. In order to read the long value page, there is a pointer in
the row of data. This error is generated when the Jet database engine
cannot properly read the long value page from the pointer present in
the data row. When viewing a row that exhibits this behavior in
Microsoft Access data-windows, the user will typically see the number
sign (#) for the entire row.

HTH

Robert Berman

[john rutherford]

read only

pessimistic - no one else can amend your records whilst you r in process
of editing them

optomistic - Two or more users can concurrently amend a record in your
recordset

You do have default locking Mechanism set correctly?
ie
Click Tools /Options Advanced Tab - No Locks
All Records
Edit Records (this should be selected)
Otherwise size of database - server performance - amount of users all may
come into play.

in article 3C36894D...@bigpond.net.au, Allen Browne at
abro...@bigpond.net.au wrote on 5/1/02 5:04 am:

[Brett Rawcliffe]

I have had the problem mentioned in the first message and it is cause
major problems
I urgently need help to solve
The previous message seems to indicate an error/corruption in a memo
field but the tables in the sub forms do not any memo fields!!

[MacDermott]

While memo fields are a common source of corruption, they are not the only
one.

Try compacting your database and see if that solves the problem.

HTH
- Turtle

"Brett Rawcliffe" <braw...@bigpond.net.au> wrote in message
news:a307fb32.02012...@posting.google.com...