UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> error 2101 - setting not valid for property    
 
   
glue
post Jan 12 2006, 01:10 PM
Post#1


UtterAccess VIP
Posts: 894
Joined: 23-March 04
From: ohio


My database just threw this error for two users 32 seconds apart:
rror 2101:
The setting you entered isn't valid for this property. To see the valid settings for this property, search the Help index for the name of the property.
Ocan't reproduce it. And the function seems foolproof to me:
(bnOkayToSave is a module level boolean variable)
CODE
Sub forceSave()
'this function is called to legally save changes to a record
On Error GoTo errForceSave
    If Dirty Then
        bnOkayToSave = True
        Dirty = False
        bnOkayToSave = False
    End If
exForceSave:
    Exit Sub
errForceSave:
    LogErr "Form_Mainform", Err.Number, Err.Description, "forceSave"
    Resume exForceSave
End Sub

any insight appreciated!
aaron
Go to the top of the page
 
GroverParkGeorge
post Jan 13 2006, 01:47 AM
Post#2


UA Admin
Posts: 33,794
Joined: 20-June 02
From: Newcastle, WA


WAG: Possibly a blip in your network caused them to lose their connection momentarily?
eorge
Go to the top of the page
 
glue
post Jan 13 2006, 12:51 PM
Post#3


UtterAccess VIP
Posts: 894
Joined: 23-March 04
From: ohio


Thanks, but it must be something else... it happened again today.
nother clue on my end is that for the first user, it happened once. For the second, four times successively (and the records are indeed saved), and the third user today, three of these clusters of four...
I'm thinking I must be missing an error handler further in that allows the error to propogate back to my forceSave function, at least that's where I'll be looking now.
HMMM...
Now I've looked into the error handlers on the form events, and that seems to be ruled out too.
I have Load, Unload, BeforeUpdate, Current, and KeyDown events, all with error handling as above. So even if one of these, triggered by saving the record, called a function without proper error handles, it wouldn't propogate back to forceSave, right?
Aaron
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    22nd October 2018 - 06:20 PM