Ever since switching servers, various users of a customer's application
have been reporting the following EDB 2 error message:

 ElevateDB Error #1201 An error occurred while
 uncompressing data (Incorrect data check).

When I first rolled out the application, the customer, which has people
in 3 geographically diverse places in the U.S., were accessing the data
from an EDB server running on Windows Server 2008 in my home office.
After a few months, they switched to using a machine in their own
office.

I recommended a server OS, but they just pulled out an old XP from the
closet and said that ought to do.  I almost refused to install it, but
after a disclaimer and some weekend testing, went ahead and did it
anyway.  After all, EDB is a lean and nimble database engine, it should
run fine, right?

So now they're getting this error and I feel like telling them, "I told
you!"  Would simply getting a newer, faster machine with more memory
and a brand new installation of XP with all but the barest of services
turned off help this situation? Or is this indicitive of more serious
issues underneath?

The application is written in Delphi 2006 with EDB 2.02 build 12.

--
David Cornelius
CorneliusConcepts.com

David,

<< Ever since switching servers, various users of a customer's application
have been reporting the following EDB 2 error message:

 ElevateDB Error #1201 An error occurred while  uncompressing data
(Incorrect data check). >>

In what context are they seeing this error message ?  During comms with the
EDB Server, or during a restore, etc. ?

--
Tim Young
Elevate Software
www.elevatesoft.com

> In what context are they seeing this error message ?  During comms
> with the EDB Server, or during a restore, etc. ?

The only thing they know is the application I wrote for them.  It's
just their daily use of it, editing invoices, generating reports, etc.

The database is backed up nightly (no reason to restore yet) and while
the tables are published, there's no synchronization happening right
now--everyone connects directly to the server.  There are two in the
office on the same LAN, and two that connect remotely.  The two in the
office are the heaviest users and have reported the problem the most.

I've never encountered the problem.  I've considered writing a test app
that creates and modifies records continuously to a test database on
the same server.  I would imagine I'd get the error eventually that way.


--
David Cornelius
CorneliusConcepts.com

David,

<< The only thing they know is the application I wrote for them.  It's just
their daily use of it, editing invoices, generating reports, etc. >>

Okay, then it sounds like a comms issue.  I would have them check their
network setup, especially on the XP server machine.

--
Tim Young
Elevate Software
www.elevatesoft.com

> << The only thing they know is the application I wrote for them.
> It's just their daily use of it, editing invoices, generating
> reports, etc. >>
>
> Okay, then it sounds like a comms issue.  I would have them check
> their network setup, especially on the XP server machine.

Thanks--I'll work on that.

--
David Cornelius
CorneliusConcepts.com