Dear Support!

I want to ask that have DBISAM 3.x versions 64 bit version? And next products?

One of our corporation have horrible "loading" of the server, and we must installed (in the prev. year) two servers because of OM error - the process memory exhausted (over 2,x GB).

But now they have many lock errors because the two dbsrvr concurrently fighting for the resources.

This meaning that they needs to restart the server (computer), and logout all of the 100-150 users on 12.00-15.00.

We have 4 kind of errors:
- "Record used by another user"
- "Record has been changed or deleted by another user"
- "Uncompression error"
- "General Lock problem"

and some AV-s on dead session removal, and in other places.

The basic problem that we cannot port (to EDB) their programs enough faster, and we must keep this customer.
We cannot do anything - because the AV's source not determinable.

Only two way we have:
a.) We install 64 bit version of the DBSrvr.exe, and then we can use more memory - not need two servers.
b.) We install test debug server (I think you sent me same tool) to get information about the source of the errors - but this is long operation.

Thanks:
  dd

durumdara wrote:

Dear Support!

I want to ask that have DBISAM 3.x versions 64 bit version? And next products?

....

I think your 64 bit question should be sent to Embarcadro.... once they delivery a 64 bit compiler existing Delphi coded products could be upgraded.... even your own product.

If your not prepared to move to EDB, why not move to DBISAM 4?

Walter

<< I want to ask that have DBISAM 3.x versions 64 bit version? And next
products? >>

No, we won't be producing any more DBISAM 3.x builds.  We will be producing
a 64-bit version of DBISAM, once Embarcadero releases a 64-bit compiler.

<< Only two way we have:
a.) We install 64 bit version of the DBSrvr.exe, and then we can use more
memory - not need two servers.
b.) We install test debug server (I think you sent me same tool) to get
information about the source of the errors - but this is long operation. >>

Actually, neither of those are options.  We don't have a 64-bit version of
the server, and we don't have a debug version of the server for DBISAM 3.x -
we have one for DBISAM 4.x, though.

Did you consider just moving them to DBISAM 4.x ?  It should be fairly
quick, and should resolve these issues.

Also, are you using FastMM4 with the DBISAM 3.x server ?  If not, then that
may be part of the problem.

--
Tim Young
Elevate Software
www.elevatesoft.com