ms access - quick way to fill or set all boolean values..[solved]

[vhelp]

SOLVED - see post # 3

Hi all. I've been away hammering on a project my boss enlisted me in. Anyway. I have a mdb database i'm working on and in one aspect of it i am utilize a grid to show and set a few values though mainly boolean. They are true/false values in a check box to make flagging the rows easier. But now i need to reset them all to no value (blank box), or false. I added a button to the form. Note, this is not the actual ms access IDE, it is a standalone short program to test something out really quick for him. I'm looking for an SQL version if possible. I can feed that into the backend code elsewhere.

I think it can be done in an update query but i'm not sure. I usually use ms access for that through the query section and then through { menu\View\SQL View } obtain the SQL text part. I know, cheating, but I can't remember everything in this beast.

Thank you very much in advance.

fields and values:

prodID  YesNo  Notes
------  -----  -----
1       true   don't run
2       true   don't run
3       false  
4       true   look both ways
5       true   its supper man
6       false  
7       true   don't run
8       true   bake me some pizza
9       true   home made pizza dough
10      true   mini pizza

[vhelp]

I think I have SQL script working:

UPDATE tbl SET tbl.yesno = False;

EDIT:
Well, it almost works. while it complete the resting to all FALSE, I also get an error message:

'Current provider does not support returning multiple recordsets from a single execution.'

I'll figure it out.

[vhelp]

SOLVED

In the windows application I was building (using delphi 7) I was using the wrong windows non-visual components to do the job.

Also, I enhanced the SQL string to only update any records who's boolean value were check-marked or True, super quick performance.

UPDATE tbl SET tbl.yesno=false WHERE tbl.yesno=true

[DB83]

No reason whatsoever why you first code would not do the job - SQL would simply ignore the rows that would not require updating. I doubt that the issue was the SQL but, as you said, the program itself since the new code simply replicates the result of the first.