AdsEnableEncryption()

clemerson · Post by **clemerson** » Thu Oct 19, 2006 11:57 am

Hi,

I used DBF open with ADS usually and I never had problems.

Now I am using AdsEnableEncryption () and this working ok

The times in some customers when the energy falls this corrupting files, and normal that using AdsEnableEncryption ()?

Clemerson

Mike Buckler · Post by **Mike Buckler** » Thu Oct 19, 2006 12:07 pm

I use AdsEnableEncryption () for last 4 years with no problems at all.
Mike Buckler

clemerson · Post by **clemerson** » Thu Oct 19, 2006 12:43 pm

Mike Buckler wrote:I use AdsEnableEncryption () for last 4 years with no problems at all.
Mike Buckler

do I use local ads and you use local ads or server?

Clemerson

clemerson · Post by **clemerson** » Thu Oct 19, 2006 3:24 pm

this and the error:

7016 Corrupt table
Problem: The specified table contains corrupted data in the file or field headers.

* ADS Local Version 8.1

Clemerson

Mike Buckler · Post by **Mike Buckler** » Thu Oct 19, 2006 9:36 pm

I use both ads server and local ads 8 with encrypted files. We have never had a problem with corruption???
Mike

James Bott · Post by **James Bott** » Thu Oct 19, 2006 10:18 pm

Clemerson,

Consider the possibility that the corruption may not be due to encryption but rather something else.

James

R.F. · Post by **R.F.** » Thu Oct 19, 2006 11:37 pm

From the ADS knowledge base:

Problem: The specified table contains corrupted data in the file or field headers.
Solution: Make sure the specified file is a valid table. Also, make sure you are not attempting to open a DBF table with an ADT table type, or vice versa.
If you have an existing data dictionary that was created with any 6.0 Beta release of Advantage, the ADT database tables are not compatible with the 6.0 release of the Advantage clients and servers. You will get a 7016 error when attempting to open those ADT tables using the Advantage 6.0 release product. A utility is provided to update those ADT tables to make them compatible with the 6.0 release of the Advantage clients and servers. The utility (update_r6b2.exe) is installed in the same directory as the Advantage Data Architect (arc32.exe) utility, and it can be called from the command line.

clemerson · Post by **clemerson** » Fri Oct 20, 2006 11:39 am

James Bott wrote:Clemerson,

Consider the possibility that the corruption may not be due to encryption but rather something else.

James

I am thinking it is another thing even.

Clemerson

clemerson · Post by **clemerson** » Fri Oct 20, 2006 11:43 am

RF wrote:From the ADS knowledge base:

Problem: The specified table contains corrupted data in the file or field headers.
Solution: Make sure the specified file is a valid table. Also, make sure you are not attempting to open a DBF table with an ADT table type, or vice versa.
If you have an existing data dictionary that was created with any 6.0 Beta release of Advantage, the ADT database tables are not compatible with the 6.0 release of the Advantage clients and servers. You will get a 7016 error when attempting to open those ADT tables using the Advantage 6.0 release product. A utility is provided to update those ADT tables to make them compatible with the 6.0 release of the Advantage clients and servers. The utility (update_r6b2.exe) is installed in the same directory as the Advantage Data Architect (arc32.exe) utility, and it can be called from the command line.

I noticed that in these customers that he gave the error before he had an older version of my software and it updated now and in the fall of energy he gave the problem, I will verify this update_r6b2.exe.

Clemerson

clemerson · Post by **clemerson** » Fri Oct 20, 2006 11:45 am

Mike Buckler wrote:I use both ads server and local ads 8 with encrypted files. We have never had a problem with corruption???
Mike

then for the comment of all no and problem of the encrypted files.

Clemerson

clemerson · Post by **clemerson** » Fri Oct 20, 2006 12:46 pm

Does a thing find strange that observed, did I open the file DBF with MED and did I verify the parts that it damaged in DBF, recorded in DBF leaves of another file temporary DBF, will it be that that help?

Clemerson