Tim

Switching to V2, trying to run my app and I get the above error. Its trying to load from a field holding a V1.09 table using the code below:

function StreamMemoToTable(Fld: string; SrcTbl: TEDBDataset; DestTbl: TEDBTable; OpenExclusive: boolean = False): boolean;
var
ms: TMemoryStream;
begin
try
 DestTbl.Close;
 DestTbl.Exclusive := True;
 ClearTable(DestTbl);
 DestTbl.Close;
 DestTbl.Exclusive := OpenExclusive;
 DestTbl.Open;
 if not SrcTbl.FieldByName(Fld).IsNull then begin
  ms := TMemoryStream.Create;
  TMemoField(SrcTbl.FieldByName(Fld)).SaveToStream(ms);
  try
   if ms.Size > 0 then begin
    DestTbl.LoadFromStream(ms); <<<<<<<<<<<<<<<<<<<<<<<< #1003
    DestTbl.Refresh;
    DestTbl.First;
   end;
  finally
   ms.Free;
  end;
 end;
 Result := True;
except
 Result := False;
end;
end;


Worked perfectly under 1.09

NULL the fields, reopen the project and do things so that the table is populated and its fine again so it looks as though there's been a change somewhere between 1.09 and V2 that hasn't been documented. Could it be anything to do with the cludge for setting a field to NULL using .Clear?


Roy Lambert

Roy,

<< Switching to V2, trying to run my app and I get the above error. Its
trying to load from a field holding a V1.09 table using the code below: >>

Okay, I'm not sure why that is in there.  It was probably done as an extra
"safe-guard" in case the format changed, but it isn't necessary.  I'll
remove it for 2.01 or the next build.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

>Okay, I'm not sure why that is in there.  It was probably done as an extra
>"safe-guard" in case the format changed, but it isn't necessary.  I'll
>remove it for 2.01 or the next build.

Hello Tim,

I'm still having this error using version 2.01 build 4. I have migrated the data from DBISAM version 4. Could that be the problem?

Regards, Ries

>Ries van der Velden <ries@pk-options.nl> wrote:

>I'm still having this error using version 2.01 build 4. I have migrated the data from DBISAM version 4. Could that be the problem?

Please ignore this last post.. The BLOB field contains a DBISAM table.. Which of course I cannot open in ElevateDB.. *stupid*

Regards, Ries

Ries


Do you have DBISAM tables stored in an ElevateDB memo field and  are trying to extract them to ElevateDB tables?

Roy Lambert [Team Elevate]