CLientDataSet - Log Changes BIG PROBLEM?

[Boot]

I have a probme, i think with the ClientDataSet. I have an application which emoploys a client-side database in form of a nested .cds file. I have a primary table which has 5 nested tables connected to it. Now here is my problem - If i turn on LogChanges on the primary table and then save the data to the .cds file i can no longer open this file. I get an error "Operation not applicable" I opened the file with a hex editor and i compared the before and after states. It appears that the file contains a "LINK_FIELD" tag along with multiple "LINK" tags na da "CHANGE_LOG" tag. Thats understandable, it probably stored the Delta in the file. My question is if it has the capability to save the file like that, while cant it open it afterwards? Whats the point of saving a file you can never open up again? Several of my users got this problem and i cant restore their client files. What is the solution here? How can i clean the file so that a client dataset can open it again? I cant even opent the file in a blank project with a simple clientdataset with no keys, field defs or any other links to my application.

 

[BobbaFet]

Hi Boot,

Maybe you should use another table in your file to log the
changes to. So that you have in fact two primary(?) tables
in your file. One for the normal stuff and one for all the
changes. I don't have an idea on how to restore your clients
files. You could try to change your way of saving these
changes.

I hope this helps,

BobbaFet Everyone has a right to my opinion.
E-mail me at cwcon@programmer.net

http://cwcon.50megs.com/

Be a nice guy 'n press that little ol'
VVV---(this one) for me ;-)

 

[Boot]

Thank you for your reply. We did correct the way changes are saved. the problem we face is that some clients out there managed to create these invalid files in the short period before the release and the patch.