I have some old code that I am looking at...
It concatenates a SQL statement to Insert into "TblB" which is executed with DoCmd.RunSQL.
Next it Updates "TblA" that is left joined to "TblB" and has a where clause that uses IS Null on one of the joined fields - a classic update on missing values. It was also executed with DoCmd.RunSQL
What happened though is all values were identified as missing where none of them should have been missing based on the data result.
Has anyone seen anything like this? Any absolute workarounds? I added a Doevents between the two but somehow I have doubts and this may not be the only case it can happen.
Other details:
This happened in a frontend with both tables local. Yes it is using "temp" tables in the frontend file.
Windows 7
Access 2013
Big corporate environment
Security set to paranoid (If you can think of it, it is probably done here)
It concatenates a SQL statement to Insert into "TblB" which is executed with DoCmd.RunSQL.
Next it Updates "TblA" that is left joined to "TblB" and has a where clause that uses IS Null on one of the joined fields - a classic update on missing values. It was also executed with DoCmd.RunSQL
What happened though is all values were identified as missing where none of them should have been missing based on the data result.
Has anyone seen anything like this? Any absolute workarounds? I added a Doevents between the two but somehow I have doubts and this may not be the only case it can happen.
Other details:
This happened in a frontend with both tables local. Yes it is using "temp" tables in the frontend file.
Windows 7
Access 2013
Big corporate environment
Security set to paranoid (If you can think of it, it is probably done here)
