billcute
asked on
Error msgbox '31005' - Access failed......
txtText1 is a form field bounded to tblMain. tblMain.Test1 is a mandatory field.
User entered a data in a text box and then removed it later for one reason or the other. User proceded to enter all other fields but skips txtTest1.
User eventually forgot to re-enter data in the txtTest1 form field. When user clicked the btnAddNew record to advance to a new record screen a msgbox flagged telling user that txtTest1 must be filled.
Also immediately and before user gets the chance to enter data in the txtTest1 form field, another Microsoft Access Error '31005' dialogbox immediately popup with the following message :
"Access failed to evaluate one or more expressions because '|'
was referenced in an expression. Only functions and properties
that are considered to be safe are allowed in expressions when
Access runs in sandbox mode."
Question:
User does not know what this new message means and how to disable the msgbox from showing in the future.
User entered a data in a text box and then removed it later for one reason or the other. User proceded to enter all other fields but skips txtTest1.
User eventually forgot to re-enter data in the txtTest1 form field. When user clicked the btnAddNew record to advance to a new record screen a msgbox flagged telling user that txtTest1 must be filled.
Also immediately and before user gets the chance to enter data in the txtTest1 form field, another Microsoft Access Error '31005' dialogbox immediately popup with the following message :
"Access failed to evaluate one or more expressions because '|'
was referenced in an expression. Only functions and properties
that are considered to be safe are allowed in expressions when
Access runs in sandbox mode."
Question:
User does not know what this new message means and how to disable the msgbox from showing in the future.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
tbsgadi:
Your suggestions seems to provide better understanding of the problem.
Your suggestions seems to provide better understanding of the problem.
"By Setting to low seems okay but what are the consequences?"
In theory, if set to Low, a 'virus' (not really) could be loaded. What that actually means is that someone could send you an MDB with an AutoExec Macro that runs a function that executes the Shell Command with deletes everything on your hard drive. This happened once circa 2002 which is why M$ implemented the macro (in)Security mess for A2003. It is and always has been a joke, because it is *easily* circumvented a number of ways ... thus ... False Security. IF ... it's Your MDB and you have control over it and you and your users are the only ones using it, then you don't really have anything to worry about. IF ... *someone else* sent you a different MDB with the above scenario ... then you could have a problem ... because the Macro Setting is Global for Access.
mx
In theory, if set to Low, a 'virus' (not really) could be loaded. What that actually means is that someone could send you an MDB with an AutoExec Macro that runs a function that executes the Shell Command with deletes everything on your hard drive. This happened once circa 2002 which is why M$ implemented the macro (in)Security mess for A2003. It is and always has been a joke, because it is *easily* circumvented a number of ways ... thus ... False Security. IF ... it's Your MDB and you have control over it and you and your users are the only ones using it, then you don't really have anything to worry about. IF ... *someone else* sent you a different MDB with the above scenario ... then you could have a problem ... because the Macro Setting is Global for Access.
mx
ASKER
MX
Thanks
Thanks
ASKER
By Setting to low seems okay but what are the consequences?