I have installed the latest version of DBISAM (v4.25b1 C/S) and now it seems
when I try to repair a remote table I always get the exception, "15002 Error
Decompressing Data".

Both Verify and Optimize work fine on the same table using the same table
component with no session or database component property changes. Other
database writing appears to be fine as well.

-Johnnie

Johnnie,

<< I have installed the latest version of DBISAM (v4.25b1 C/S) and now it
seems when I try to repair a remote table I always get the exception, "15002
Error Decompressing Data".

Both Verify and Optimize work fine on the same table using the same table
component with no session or database component property changes. Other
database writing appears to be fine as well. >>

I can't replicate that here.  What version of the database server are you
using ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:D347FFA3-87A4-4BA8-BF50-8AD8BF6E3A1B@news.elevatesoft.com...
> Johnnie,
>
> << I have installed the latest version of DBISAM (v4.25b1 C/S) and now it
> seems when I try to repair a remote table I always get the exception,
> "15002 Error Decompressing Data".
>
> Both Verify and Optimize work fine on the same table using the same table
> component with no session or database component property changes. Other
> database writing appears to be fine as well. >>
>
> I can't replicate that here.  What version of the database server are you
> using ?

I am using a version 4.24 server.

Johnnie,

<< I am using a version 4.24 server.  >>

Hmm, I just tried it with that configuration and it still works fine.  Does
this happen every single time you do a repair, or is it sporadic ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:749D572A-EE75-409F-B9C6-1834C1C2E8DB@news.elevatesoft.com...
> << I am using a version 4.24 server.  >>
>
> Hmm, I just tried it with that configuration and it still works fine.
> Does this happen every single time you do a repair, or is it sporadic ?

I have a general repair routine for all my tables and it happens on every
one of them. I am using one TDBISAMTable component and passing the table
name before repairing. I'll try the latest DBSys and trace my code to look
for any other problems. So, I'll get back to you with more information.

-Johnnie

Johnnie,

<< I have a general repair routine for all my tables and it happens on every
one of them. I am using one TDBISAMTable component and passing the table
name before repairing. I'll try the latest DBSys and trace my code to look
for any other problems. So, I'll get back to you with more information. >>

I wish I could be more helpful, but I can't replicate it here.  However,
this is definitely an error that you shouldn't be able to cause no matter
what you do, so it is a fault in DBISAM somewhere.

--
Tim Young
Elevate Software
www.elevatesoft.com