Lucian,

<< Bothering you with something else, I may be doing something wrong, not
sure. I am backing up a 177MB database. I tried different compression values
and my results are:

compression 1, time 33 sec (supposedly) best speed
compression 6, time 23 sec
compression 9, time 23 sec

the resulting file size is precisely the same to the byte, 177MB. I see
absolutely NO compression. Am I doing something wrong? >>

Are the tables encrypted at all ?

--
Tim Young
Elevate Software
www.elevatesoft.com

> Are the tables encrypted at all ?

Yes, all of them. That's the thing?

Lucian

Lucian,

<< Yes, all of them. That's the thing? >>

Yep, you're going to get 0% compression with encrypted tables due to the
fact that the data is completely randomized.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Yep, you're going to get 0% compression with encrypted tables due to
> the fact that the data is completely randomized.

Ok, thanks
Lucian

> What risk are you referring to specifically - the issue with mixing
> versions ?

My code automatically restructures tables ... the thing is sometime
users, when they encounter even small problems, they switch to an
earlier build (hapened this week at some firm), I think in this case
the blobs would be wiped out when downgrading the build (I do check
some table versions, but we relased some earlier beta and I am not sure
I was consistent with that every time).

I suppose I'll do some tests and upgrade after we're out of beta (end
of july).

Lucian

Lucian,

<< My code automatically restructures tables ... the thing is sometime
users, when they encounter even small problems, they switch to an earlier
build (hapened this week at some firm), I think in this case the blobs would
be wiped out when downgrading the build (I do check some table versions, but
we relased some earlier beta and I am not sure I was consistent with that
every time). >>

Ah, yes.  Unfortunately, you're going to have that problem until you get a
couple of versions in that use 4.28 or higher.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Ah, yes.  Unfortunately, you're going to have that problem until you
> get a couple of versions in that use 4.28 or higher.

Tim,

So regarding the blobs, I just want to clarify this: I upgraded to 4.28
build 4, from 4.27. None of the tables that have blobs have been
restructured. Is this normal? I understand that I can not use apps
built with 4.27 on tables that have been open/updated by an app which
was built with 4.28. So if all our customers upgrade to 4.28, the only
problem would be they can't go back to a previous built (which we don't
care about since that was a beta anyway)

thanks,
Lucian

p.s. is the initial issue with CompareDataTables still analyzed? or
what is the resolution?

> So regarding the blobs, I just want to clarify this...


In other words do I have to force a call to UpgradeTable or not?

Lucian

Lucian,

<< So regarding the blobs, I just want to clarify this: I upgraded to 4.28
build 4, from 4.27. None of the tables that have blobs have been
restructured. Is this normal? I understand that I can not use apps built
with 4.27 on tables that have been open/updated by an app which was built
with 4.28. So if all our customers upgrade to 4.28, the only problem would
be they can't go back to a previous built (which we don't care about since
that was a beta anyway) >>

Yes, it is normal.  You don't need to call UpgradeTable or anything else.
You simply need to make sure that you use 4.28 or higher.

<< p.s. is the initial issue with CompareDataTables still analyzed? or what
is the resolution? >>

The fix will be included in the next DBISAM build, which looks like it will
be later this week.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thank you,

Lucian