Though the advice may be valid, it does not answer the question. I already know how to devise parameter queries, etc. so I won't ask for that. I just wanted to know about the why's and how's of DESIGN mode vs. SQL mode for a query.
By the way, one of the reasons that the client chose Access as...
The queries are actually the client's, not mine. When we added some tables to the db, we were asked for help in incorporating them into some existing queries. They were already using DESIGN mode to create and change criteria for queries. That is when we found that the sql was being changed...
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...
The variable is in a code module as 'public' and 'option explicit' is set in all class modules. What is the difference between 'public' and 'global'. The help definition of 'public' is exactly what I am looking for.
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.