I have a query designed in Access SQL mode. It contains a series of: where ... and where...this or where...this and this and this. The query runs correctly. If I then use Access DESIGN mode to change a criteria value, the query fails to run correctly. Looking at the SQL, it has been totally...
I have a public variable 'userid' which is set in 1 place only. It is used throughout the program to update records, but occasionally becomes blank. Is there any known problem with public memory getting overridden (such as not returning recordsets to nothing, thus hogging mem)?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.