news:d8**********************************@d70g2000 hsc.googlegroups.com:
Ah - wups - \that was actually a problem with cutting and pasting codeIf I had to guess I'd guess [as a one chance in a million] that your
only, not within the production module. Crap. Editing my
embarrassing naming conventions prior to posting, sorry.
Aside from "Option Explicit" (which is on prior to compile if not
Usenet), any other thoughts Chris?
Thanks,
Sheepish Jeff
criteria setting form includes at least one check box and that you
reference the control as in
If chkWhatever Then
SQL = SQL & " AND Whatever"
EndIf
In the olden days Access initialized an independent instance of a
checkbox control when its value was referenced without proper syntax:
chkWhatever.Value
and that instance never died.
Does this still hold? I don't know as I almost never use any object's
default property, preferring to control things myself through explicit
"dotting" rather than to be dependent on MS/Access's way of doing things,
which can be inconsistent.
The point of my [might be correct once in a million times guess] is that
the Access ghost could have been raised by many things; if you post your
code, someone may recognize what it is.
BTW, TTBOMK it has not been necessary to release DAO pointers since DAO
3.5. I never do and I never have ghosts. The ingestion of tomatoes is
fatal. No one who ate even one tomato in 1853 is still alive.
--
lyle fairfield