Lee
If the recordset is using data displayed in the form that would probably be your
conflict. Could that be it?
Regards,
Bill
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Lee
Sent: Thursday, September 20, 2012 9:45 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Error 3197 write conflict
Hi,
I have a user getting a 3197 error, the description of the error makes it look
like a write conflict.
However, after reviewing the code that causes the error, it doesn't make any
sense because there is no record updating involved. It takes a predefined select
statement, reads the form filter property and uses that to create a where
statement, updates a query def stored in each user's front end (the db is split,
data is on the network), and does a transfer spreadsheet to a file the user
selects the name/location of.
I checked my code to make sure I'm not leaving any recordsets open anywhere that
might be hanging it and they're all closed at the end of each routine.
here is one form where data can be edited that is bound to a query (which is
basically select * from table), but the form is modal so they wouldn't be able
to leave it open and work on anything underneath it.
Default record locking in the front ends in tools>>options>>advanced is "no
locks", and "open using record level locking" is unchecked.
Any ideas what could be causing error 3197?
Thanks
-Lee
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar