Optimistic Locking - Bound Form - Access 2000

[KenReay]

Hi

I am using Optimistic Locking (.RecordLocks = None), with a bound form. Does anyone know if it is possible to trap the standard Access message given when two users change same record (ie the message giving three choices Save and overwrite other users changes, discard changes, save to clipboard), my present user base find this too complex, so I would like to replace is with a custom message giving fewer choices



Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[gavinjb]

From what I remember that is an Data Error (can only be trapped through the On Error Event), so you should be able to trap it through the On Error Event.

You will need to watch for the DataErr No, if you dont know the number just add an msgbox DataErr.

You will need to add an response = acDataErrContinue (no display of standard message) or repsonse = acDataErrDisplay

Hope this helps


Gavin,

 

[KenReay]

Hi

Could you give an example

I have an OnError GoTo statement in, but no error is being trapped

I have the code in the onclick event of a Save command button

Procedure CmdSave_Click
On Error GoTo Error_Click
DoCmd.RunCommand acCmdSaveRecord
Exit_Click:
exit sub
Error_click:
' never get here
End Sub

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[ZmrAbdulla]

Ken,
Did you try to get all the access errors in a list

http://support.microsoft.com/?kbid=268721

may be useful to you or someone else
regards

Zameer Abdulla

http://www.geocities.com/zameerabd/

 

[hymn]

below is for Pessimistic but you might be able to amend

http://msdn.microsoft.com/library/d...y/en-us/office97/html/output/F1/D2/S5A2C1.asp

Hope this helps
Hymn

 

[KenReay]

Hi

Thanks for the link Hymn, more knowledge never hurts!

That example was for updating via recordset, so I will store it away for future use. In the meantime I think I have what I am looking for, just testing it out now, what I have done is briefly as follows:

Put code in the Form_Error event, trap the errors (DateErr), 7787, 7878, 3262. These are Jet Errors not Access errors
Used the Response parameter to change the standard behaviour, using acDataErrContinue and acDataErrDisplay constants to display my owm message and handle the situation

As I say, I am testing the result now, looks promising

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[RoyVidar]

Hi!

Think this is dataerr 7787, but do a msgbox DataErr within the forms on error event to be sure, then it might look like this:

[tt]private sub form_error(dataerr as integer, response as integer)
if dataerr=7787 then
response=acdataerrcontinue
' disable the default msgbox
end if
end sub[/tt]

- but this will throw an exeption at the save command too, perhaps the 3197? Then also trap for that, perhaps something like this:

[tt]Procedure CmdSave_Click
On Error GoTo Error_Click
DoCmd.RunCommand acCmdSaveRecord
Exit_Click:
exit sub
Error_click:
if err.number=3197 then
msgbox "you and another... not saved..."
else
msgbox err.description
end if
resume Exit_Click
' should get here
End Sub[/tt]

Think the challege is that the dataerr is evaluated before the saveroutine has a chance to throw an exeption, but trapping for it like this might do.

Another thing, sometimes those savecommands doesn't throw an exeption, see osing data when you close a form - sometimes using his method is quaranteed to throw an exeption should there be errors in the save process

Roy-Vidar

 

[RoyVidar]

Hmpf - typing to slow, again

Roy-Vidar