If I save a memory table to a disk file using .SaveToStream() in version 4.25..... will this disk file still be compatible with newer versions of DBISAM?

Thanks,

Dale

Good question and while i don't know the general answer i can say from experience that between different builds of same version it's OK (for example we have saved using 4.29 and loaded using in 4.36).

The question would be around major file compatibility breaking changes - like 4.27 blob change - so for example saving in 4.25 and loading in anything newer than 4.28. Not sure about this one though i have a feeling Tim was smart enough to account for this - i know i can load into a table that has additional columns added.

Usual caveats of using this still apply - it's all in memory so it might not be suitable for large tables - but that's not a compatibility issue.

Raul


<<
Dale Derix wrote:
If I save a memory table to a disk file using .SaveToStream() in version 4.25..... will this disk file still be compatible with newer versions of DBISAM?
>>

Dale,

<< If I save a memory table to a disk file using .SaveToStream() in version
4.25..... will this disk file still be compatible with newer versions of
DBISAM? >>

As long as the streams are all from DBISAM 4.x, then yes, you will be okay.

Tim Young
Elevate Software
www.elevatesoft.com