(Cross posted to Sesame Online Support)

I'd like some more information on multi-user locking, as it's causing me a big headache.  On my form, I do a number of lookups in the On Form Load event.  For reasons I have yet to determine, these lookups fail to function when accessing a record that is current locked by another user (either the lookups fail or the locking disallows the form fields to be programatically populated).  The problem is that I do writes using XResultSetValue during the On Form Exit event.  Some of the writes utilize data that was supposed to have been loaded in the On Form Load event.  Since the data failed to load, the writes I have in On Form Exit effectively overwrite my data with empty data.  Very very bad.

One workaround I tried was to check the locked status of the form's result set.  Unfortunately, there was no consistency in the locked status.  Sometime it would say the form was locked, and sometime unlocked, with no consistent pattern.  The code I used to check the locked status in the On Form Load event was:

If @XResultSetLocked( @XResultSetCurrentForm() ) = 0 Then
	WriteLn( "Locked Status = Not Locked" )
Else
	WriteLn( "Locked Status = Locked" ) 

I don't care if my lookups fail, as long as I have some mechanism to use to know to turn off my code in the On Form Exit event.  I'd prefer that my lookups succeed, but right now it is much more important that my data doesn't get blown away.  Unfortunately, this whole situation is difficult to test, since it can't be tested using the Designer's Preview mode.

Hammer wrote on Feb 18^th, 2008 at 1:23am:

Sorry.  On Form Entry.

Hammer wrote on Feb 18^th, 2008 at 2:18am:

I tested further and confirmed that it's not the lookups that are failing but the fields that are being disallowed from being populated.  Here's a relevant code fragment from my On Form Entry event:

txtZip = @XResultSetValue(vintResultSetIn, "fZip")
WriteLn( "Zip from database: " + @XResultSetValue(vintResultSetIn, "fZip"))
WriteLn( "Zip in document: " + txtZip ) 

That produces the following output:

Zip from database: 99999
Zip in document:

Note again that this only occurs when the form is locked due to a multi-user issue.  It works fine otherwise.

Do you have elements on this form which are bound?

OK. We'll see about a @Locked function of some sort.  Meanwhile, people usually do this by checking the read only state of a bound element that is not usually read-only. If it is read-only, then the record is locked.

MP wrote on Feb 18^th, 2008 at 2:09pm:

Your workaround sounds fine. You may also want to check On Form Exit before you do the action that is causing the problem.