|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I have a multi user application, running on A2002 in Windows XP.
User/group security is in place. I am receiving a record locking
message which seems a bit odd. It appears when the app attempts to add
text to a memo field and save the current record. The error is 3202
"Could not save; currently locked by another user". The text,
incidentally, IS saved, despite the error message.
Now, my understanding is that with password security enabled, the error
message should display the user and machine creating the conflict, but
that is not the case here. It seems to be some sort of generic lock.
I've examined the .ldb file, and no one appears to be in the file as
"Admin", or anything else odd.
If I go directly to the table and edit the field, there is no problem.
But when I use the GUI, up the error pops.
The code is very basic. txtNewNote is an unbound text box which
accepts the new text. txtLoaNotes is a locked text box that displays
the current contents of the memo field (I don't allow users to directly
input text bacause we had a memo-field corruption problem in the past).
SignNote is just a small callout which returns the user's name and a
date stamp as text.
If txtNewNote & "" <> "" Then
txtLoaNotes = txtLoaNotes & txtNewNote & SignNote() & _
vbCrLf &
"------------------------------------------------------------" & vbCrLf
txtNewNote = ""
DoCmd.RunCommand acCmdSaveRecord
txtNewNote.SetFocus
End If
The error occurs on the DoCmd statement.
Anyone have any ideas as to what's occurring?
|
|
I should add that having all users log out of the file resolved the
problem: no more error. But this happened twice before in the last
week, and I haven't modified the data or database in any way I've
repaired and compacted, and imported everything into clean .mdb files.
But I'm curious as to what is happening and why, and how it might be
prevented.
|
|
|
|
Yes, it's split: FE on the workstation, and BE and mdw on the network.
What's really got me stumped is that I could edit the field directly in
the table with no error, but going through a form, i get the error. I
even tried importing the objects and tables into fresh files: but it
happened again yesterday.
Could a corrupt .ldb cause this? As the problem vanished when I kicked
everyone out, this seems like a possibility: but how that would work, I
don't know. I thought the .ldb just stored the user and machine names,
and Jet took care of tracking the record locks.
|
|
Look to the before_update/after_update and current events
of the form: code there sometimes causes problems like this.
Simplify the form right down: strip all the other code off the
form. If there is still a problem, delete the other controls
until you find the problem.
(david)
<kestrel_mw[ at ]yahoo.com> wrote in message
news:1135274014.007833.299630[ at ]g47g2000cwa.googlegroups.com...
[Quoted Text] > I have a multi user application, running on A2002 in Windows XP.
> User/group security is in place. I am receiving a record locking
> message which seems a bit odd. It appears when the app attempts to add
> text to a memo field and save the current record. The error is 3202
> "Could not save; currently locked by another user". The text,
> incidentally, IS saved, despite the error message.
>
> Now, my understanding is that with password security enabled, the error
> message should display the user and machine creating the conflict, but
> that is not the case here. It seems to be some sort of generic lock.
> I've examined the .ldb file, and no one appears to be in the file as
> "Admin", or anything else odd.
>
> If I go directly to the table and edit the field, there is no problem.
> But when I use the GUI, up the error pops.
>
> The code is very basic. txtNewNote is an unbound text box which
> accepts the new text. txtLoaNotes is a locked text box that displays
> the current contents of the memo field (I don't allow users to directly
> input text bacause we had a memo-field corruption problem in the past).
> SignNote is just a small callout which returns the user's name and a
> date stamp as text.
>
> If txtNewNote & "" <> "" Then
> txtLoaNotes = txtLoaNotes & txtNewNote & SignNote() & _
> vbCrLf &
> "------------------------------------------------------------" & vbCrLf
> txtNewNote = ""
> DoCmd.RunCommand acCmdSaveRecord
> txtNewNote.SetFocus
> End If
>
> The error occurs on the DoCmd statement.
>
> Anyone have any ideas as to what's occurring?
>
|
|
Try compiling your code...
"david[ at ]epsomdotcomdotau" wrote:
[Quoted Text] > Look to the before_update/after_update and current events
> of the form: code there sometimes causes problems like this.
>
> Simplify the form right down: strip all the other code off the
> form. If there is still a problem, delete the other controls
> until you find the problem.
>
> (david)
>
>
>
>
> <kestrel_mw[ at ]yahoo.com> wrote in message
> news:1135274014.007833.299630[ at ]g47g2000cwa.googlegroups.com...
> > I have a multi user application, running on A2002 in Windows XP.
> > User/group security is in place. I am receiving a record locking
> > message which seems a bit odd. It appears when the app attempts to add
> > text to a memo field and save the current record. The error is 3202
> > "Could not save; currently locked by another user". The text,
> > incidentally, IS saved, despite the error message.
> >
> > Now, my understanding is that with password security enabled, the error
> > message should display the user and machine creating the conflict, but
> > that is not the case here. It seems to be some sort of generic lock.
> > I've examined the .ldb file, and no one appears to be in the file as
> > "Admin", or anything else odd.
> >
> > If I go directly to the table and edit the field, there is no problem.
> > But when I use the GUI, up the error pops.
> >
> > The code is very basic. txtNewNote is an unbound text box which
> > accepts the new text. txtLoaNotes is a locked text box that displays
> > the current contents of the memo field (I don't allow users to directly
> > input text bacause we had a memo-field corruption problem in the past).
> > SignNote is just a small callout which returns the user's name and a
> > date stamp as text.
> >
> > If txtNewNote & "" <> "" Then
> > txtLoaNotes = txtLoaNotes & txtNewNote & SignNote() & _
> > vbCrLf &
> > "------------------------------------------------------------" & vbCrLf
> > txtNewNote = ""
> > DoCmd.RunCommand acCmdSaveRecord
> > txtNewNote.SetFocus
> > End If
> >
> > The error occurs on the DoCmd statement.
> >
> > Anyone have any ideas as to what's occurring?
> >
>
>
>
|
|
|