🚀 go-pugleaf

Always be sure to close the recordset before.....
and you'll remove most of the errors.....

maybe the error mentionned by Steve will still be there (haven't tried it)


db->ADOQuery1->Close();
db->ADOQuery1->SQL->Add( "DELETE FROM TABLE1" );
db->ADOQuery1->ExecSQL();



Arnie Mauer <amauer@vrms.com> wrote in message news:3beac47b_2@dnews...
> I've had the problem too.  It seems reusing TADOQuery objects and mixing
> Open() with ExecSQL will cause problems.  We usually get an "Object was
> open" error.
>
> We've been going through the code and creating and deleting the queries
> where we need them.
>
> - Arnie
>
> "Steve Love" <steve.love2@virgin.net> wrote in message
> news:20011107.11520368@sl.engineering...
> Hi all,
> I recently applied the ADOExpress patch to get around the Bof/Eof problem
> in MDAC 2.6. I'm now experiencing a EAccessViolation for a
> TADOQuery->ExecSQL().
>
> I'm assuming it's MDAC - I'm using Win2k/Office2k, and this problem is
> not reproducable on other machines of similar config, running earlier
> MDAC versions (2.1 or 2.5 being popular).
>
> Anybody come across this one?
>
> Cheers
> Steve
>
>