> Crap, it turns out that the wrong mailing list was used for the email.  It
> excluded DBISAM customers that are also ElevateDB customers.  I'll make
> sure that another one is sent out immediately.

Aah... that answers a lot.. Thanks for letting us know!

Cheers

Adam.

Just to be sure, I can upgrade from 4.26 to the latest DBISAM, recompiling
both the app and server, with no problems?


On 6/23/09 10:19 AM, in article
50D7362E-8504-4065-B4E7-609B6031B54C@news.elevatesoft.com, "Tim Young
[Elevate Software]" <timyoung@elevatesoft.com> wrote:

> Yes.  You should not have any further issues with BLOBs using the 4.28 B3
> release and any subsequent releases.

David,

<< Just to be sure, I can upgrade from 4.26 to the latest DBISAM,
recompiling both the app and server, with no problems? >>

Yes, there is no need for any format changes to the tables.

--
Tim Young
Elevate Software
www.elevatesoft.com

TIM - sorry to bring this up from the past, but I'm in this boat right now and also want to make damn sure I understand before releasing an update to my app with the latest version of DBISAM.

The app the guys use now to create, add, update their table (and it's components) is definitely Pre-4.28.

So if I send them a new recompiled app say with the latest 4.29 build....will that cause any problems reading/writing to those older tables...or is it simply just a case of recompiling the app with the newer components and everything will work fine?  ...or

Do I need to physically do something to those older tables....like a "repair" job to make sure they work right with 4.29?

I just want to make sure as I would be in deep shit if they use this version and then they can't pull up the tables/records with BLOB fields or it causes them to be corrupted esp. since those databases are 1/2 way around the world from me!

Many Thanks,
Fred

Fred

<<
So if I send them a new recompiled app say with the latest 4.29
build....will that cause any problems reading/writing to those older tables
>>
No. This will not cause any problems

<<
is it simply just a case of recompiling the app with the newer components
and everything will work fine?  ...or
>>
Yes

<<
Do I need to physically do something to those older tables....like a
"repair" job to make sure they work right with 4.29?
>>
No. You do not need to do anything except compiling your application with
the newer version.

But...
After writing data using 4.29 then you CAN NOT access the data using 4.28
anymore because it will corrupt your data. This only happen if you write
anything in memo fields. If there is no memo field involved or you just read
the table then you can mix the version without problems.

Eduardo

Cool...sounds easy, Eduardo....just don't go back to 4.27 or before once data is written in a 4.28 or newer table.

Got it.  Many Thanks for the clarification, Eduardo!

Cheers,
Fred

Fred,

<< Do I need to physically do something to those older tables....like a
"repair" job to make sure they work right with 4.29? >>

No, just make sure that all client/server applications that directly access
the tables are using 4.29 or higher, and you'll be all set.

--
Tim Young
Elevate Software
www.elevatesoft.com