Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Error #15002 Error uncompressing data (stRemote ONLY)
Fri, Jun 19 2009 10:11 AMPermanent Link

Mike O'Grady
I have an application that has been working fine for many years. Recently, a customer sent
me some databases to have a look at a problem and I got error 15002 when working in C/S
mode on a specific table. The problem only occurs in stRemote mode and only with the
tables that the customer sent to me. In stLocal mode, it works fine. I tried repairing,
and altering and saving the table to no avail.

Although it works fine with other customers tables, it might be something I am doing. The
sequence of events is as follows:

1. Open the table using a DBISAMTable component and find a specific record. (works fine)
2. Using some values from the table, set parameters in a DBISAMQuery component which runs
a simple SQL on the same table.
3. Open the DBISAMQuery (fails at this point)

The query is requesting a live result set. If I change this, the error does not occur, but
I need a live result set.
It is not a comms problem because the server, database, and client are on the same PC.
There are no BLOBS in the table. I was using compression, but I switched it off and it
didn't make any difference. The connection is encrypted.

I am on D7 and DBISAM V4.16 (I know I should upgrade but what can I say!)

It seems to me that the table is the problem, but it works in stLocal mode and the repair
utility doesn't seem to find anything wrong.

Any clues on what it could be? I'm tearing my hair out.

Mike
Fri, Jun 19 2009 11:38 AMPermanent Link

"Robert"

"Mike O'Grady" <mikeogrady@aquilatechnology.com> wrote in message
news:6C2EFB7F-F628-4642-9021-2E1CFDD73C93@news.elevatesoft.com...
>I have an application that has been working fine for many years. Recently,
>a customer sent
> me some databases to have a look at a problem and I got error 15002 when
> working in C/S
> mode on a specific table. The problem only occurs in stRemote mode and
> only with the
> tables that the customer sent to me. In stLocal mode, it works fine. I
> tried repairing,
> and altering and saving the table to no avail.
>
> Although it works fine with other customers tables, it might be something
> I am doing. The
> sequence of events is as follows:
>
> 1. Open the table using a DBISAMTable component and find a specific
> record. (works fine)
> 2. Using some values from the table, set parameters in a DBISAMQuery
> component which runs
> a simple SQL on the same table.
> 3. Open the DBISAMQuery (fails at this point)
>
> The query is requesting a live result set. If I change this, the error
> does not occur, but
> I need a live result set.
> It is not a comms problem because the server, database, and client are on
> the same PC.
> There are no BLOBS in the table. I was using compression, but I switched
> it off and it
> didn't make any difference. The connection is encrypted.
>
> I am on D7 and DBISAM V4.16 (I know I should upgrade but what can I say!)
>
> It seems to me that the table is the problem, but it works in stLocal mode
> and the repair
> utility doesn't seem to find anything wrong.
>

1. Have you run the repair in stRemote?
2. If you simulate the same situation in DBSYS, do you get the same error?
3. If the answer to 2 is yes, does it still fail if you change the query
(for example to select * from table)?
4. If you're still lost, can you post the table in binaries so that someone
can check it with a more current version of DBISAM?

Robert


Fri, Jun 19 2009 12:08 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Mike,

<< The query is requesting a live result set. If I change this, the error
does not occur, but I need a live result set. It is not a comms problem
because the server, database, and client are on the same PC. There are no
BLOBS in the table. I was using compression, but I switched it off and it
didn't make any difference. The connection is encrypted.

I am on D7 and DBISAM V4.16 (I know I should upgrade but what can I say!)
>>

Can you send me an example of this ?  I suspect that this has been fixed
already, but I would need to test it to know for sure.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jun 19 2009 12:21 PMPermanent Link

Mike O'Grady
"Tim Young [Elevate Software]" wrote:

>Mike,

>Can you send me an example of this ?  I suspect that this has been fixed
>already, but I would need to test it to know for sure.

Hi Tim,

I assume that by "example", you mean the table. I also assume that if I
attach it to my reply, it will be ok. Two assumptions - that's asking for
grief!

Thanks,
Mike
Fri, Jun 19 2009 12:25 PMPermanent Link

Mike O'Grady
"Robert" wrote:

>1. Have you run the repair in stRemote?
>2. If you simulate the same situation in DBSYS, do you get the same error?
>3. If the answer to 2 is yes, does it still fail if you change the query
>(for example to select * from table)?
>4. If you're still lost, can you post the table in binaries so that someone
>can check it with a more current version of DBISAM?

Robert

I didn't try the repair in stRemote until you suggested it - no joy.
If I simulate the problem in DBSYS, I don't get the error.

Tim has offered to have a look at it so I'm in good hands.

Thanks
Mike
Mon, Jun 22 2009 5:33 AMPermanent Link

Mike O'Grady
Just to close out this issue, Tim suggested that I upgrade to the latest release. I did
that and it fixed the problem.

Thanks,
Mike
Image