🚀 go-pugleaf

Yes,
I'm able to do that, but it is not a Stored proc, it is a TADORecordset....

Just to be sure the patch was installed properly,

Open the file adodb.pas (in ($BCB)\Source\vcl)
and check the InternalClose procedure..

it should look like that
  BindFields(False);
  if DefaultFields then DestroyFields;
  FIndexFields.Clear;
  DestroyLookupCursor;
  if stOpen in RecordsetState then
  begin
    if FEventsID > 0 then
    begin
      OleCheck(ConnectionPoint.UnAdvise(FEventsID));
      FEventsID := 0;
    end;
  end;
  FFindCursor := nil;
  FRecordsetObject := nil;
  FFilterGroup := fgUnassigned;
  FDetailFilter := '';
  SetConnectionFlag(cfOpen, False);

and not

  BindFields(False);
  if DefaultFields then DestroyFields;
  FIndexFields.Clear;
  DestroyLookupCursor;
  if stOpen in RecordsetState then
  begin
    Recordset.CancelUpdate;                                **** HERE CAUSED
THE PROBLEM ****
    if FEventsID > 0 then
    begin
      OleCheck(ConnectionPoint.UnAdvise(FEventsID));
      FEventsID := 0;
    end;
    Recordset.Close;
  end;
  FFindCursor := nil;
  FRecordsetObject := nil;
  FFilterGroup := fgUnassigned;
  FDetailFilter := '';
  SetConnectionFlag(cfOpen, False);


Hope it helps
Rick


David Latham <dlatham@qwest.net> wrote in message news:3a6e1ec5$1_2@dnews...
> Hi Rick,
>
> I did apply that patch and continued to get the error even after the
patch.
> Are you able to set the Active property to false on an inactive, empty
> dataset without generating the error?
>
> Thanks for the reply,
>
> Dave
>
>
>
>