Not really sure where I should ask this, and I'm sure the answer is already on the forums somewhere, but...
I am converting ms access 2003 split f.e./b.e. to ms access 2010 f.e./ms sql 2012 b.e. I'm deploying to win7/64 bit desktops running 32-bit office 2010.
I've run into a number of issues getting the error message about trying to assign a null to a non-variant datatype. The access front end vba would prevent that issue from arising before the record was saved, but it appears that sql server is checking the value before any of my access f.e. vba code runs, so all my validation code appears to be ineffective, now.
Is my assessment correct? Is sql server trying to validate the entries whenever the user leaves a data control bound to a table/query column (but before the user attempts to save the record via the form)? If so, is there a way around this without having to change all the data types to variant? Did I miss some event in access that can actually be used to catch the problem before sql server jumps in?
Just for full disclosure, the issue arises when a user begins to type a value into a form control but then deletes what they have typed.
Thanks for any suggestions.
T
I am converting ms access 2003 split f.e./b.e. to ms access 2010 f.e./ms sql 2012 b.e. I'm deploying to win7/64 bit desktops running 32-bit office 2010.
I've run into a number of issues getting the error message about trying to assign a null to a non-variant datatype. The access front end vba would prevent that issue from arising before the record was saved, but it appears that sql server is checking the value before any of my access f.e. vba code runs, so all my validation code appears to be ineffective, now.
Is my assessment correct? Is sql server trying to validate the entries whenever the user leaves a data control bound to a table/query column (but before the user attempts to save the record via the form)? If so, is there a way around this without having to change all the data types to variant? Did I miss some event in access that can actually be used to catch the problem before sql server jumps in?
Just for full disclosure, the issue arises when a user begins to type a value into a form control but then deletes what they have typed.
Thanks for any suggestions.
T