Using a query instead of a SQL string with DAO

[ChrisO]

GraeagleBill…



>>Bottom line here is<<

Incorrect again; the real problem here is that you assume that you are correct.

That’s a fatal flaw in logic when dealing with computers. People can be pedantic, obnoxious or whatever but computers don’t even care. As people we have to comply with the computer because the computer is not going to change to suite our personal whims.

Push on with 'any sense of bravado' and the computer will quote a line by Al Jolson from the Jazz Singer; "you ain't heard nothin' yet".

Edit:
any other sense of bravado
was changed to…
any sense of bravado

Chris.

[GraeagleBill]

Chris,
I'll try to address each of your questions Monday morning.
Thanks,
Bill

[GraeagleBill]

Hi Chris,

You wrote:
Please explain the following:-
Why are you using Allen's DAO sample as a frame of reference in post #1? Just wanted to provide some example context in which my code would be running.
Why did debug report Empty in post #3? Because the query name WAS NOT inclosed in quotes.
How the quotes were missing around QbroadcastGroups in post #4. Again, the whole problem with the OpenRecordset statement was the absence of quotes around the query name.
The suggested fix in post #5 worked. Yes, as soon as I enclosed the query name in quotes.
That fix was confirmed in post #6. Yes
Why must it be in post #6. Not sure what the confusion is here?
Why you would need to ‘always code my modules’ in post #9 if it was turned on by default? I did not yet know how to make that the default for all VBA.

Are you now saying QbroadcastGroups as a variable (without the quotes) was declared outside of the procedure? QBroadcastGroups is the name of a query.
Are you still saying that it must be something else? I think my responses here are outdated, as the issue got resolved with putting quotes around the query name.

Thanks for you help,
Bill

[ChrisO]

Bill, I know all that…

Post #7
>>QbroadcastGroups is a variable and without Option Explicit it is defined as a Variant and initialized to Empty.<<

Post #9
>>Just as a FYI, I always code my modules "Option Explicit" so I'll catch problems whenever I compile.<<



When you ran the code Option Explicit was not turned on else it would have raised a compile error on the undeclared variable. So you don’t always use Option Explicit.

Bill, if you want help from other people you will have to tell them the facts.

Chris.

[GraeagleBill]

Got it, thanks,
Bill