🚀 go-pugleaf

> 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).

In an update to this, I've managed to re-create the problem in a small 
program. It occurs when re-using a TADOQuery component under MDAC 2.6 
and above:

1) Create a standard application.
2) Create a data module, and add a ADOConnection and ADOQuery component. 
Attach
	to your favourite database.
3) Make a pointer to the data module a member of the form class, and 
create it
	using new in the form's constructor with Application as the owner; 
	delete it in the dtr.
3) Add 2 buttons to the form, and add the following code:

void __fastcall TForm1::Button1Click( TObject * Sender )
{
	db->ADOQuery1->Active = false;
	db->ADOQuery1->SQL->Clear();
	db->ADOQuery1->SQL->Add( "SELECT * FROM TABLE1" );
	db->ADOQuery1->Active = true;
}

void __fastcall TForm1::Button2Click( TObject * Sender )
{
	db->ADOQuery1->Active = false;
	db->ADOQuery1->SQL->Clear();
	
	//
	// This can be any update query AFAICT
	//
	db->ADOQuery1->SQL->Add( "DELETE FROM TABLE1" );
	db->ADOQuery1->ExecSQL();
}

Run the program. Clicking button1 several times is OK. So is clicking 
Button2. 
The error occurs when I click Button1 followed by Button2 – i.e. A SELECT 
query
followed by an UPDATE query. In reverse, no errors occur.

> Anybody come across this one?

> Cheers
> Steve

Steve