Thank you, Barton! I found out the hard way, when I successfully loaded the metadata and data stored in an "outsider" file to a TClientDataset newly created on the fly, and operations based on indexes that were set in the original TClientDataset whose information had been saved to disk and loaded from disk to our new TClientDataset, have all failed because the indexes don't exist on the new ClientDataset. You are right when you say that "SaveToFile" doesn't store the "Delphi object's attributes." But, there must be way one can save most if not all of those attrinutes to disk for re-use if or when needed. Don't you think so?
Emmanuel --- In [email protected], Barton Bresnik <bbres...@...> wrote: > > Emmanuel, > TClientDataSet SaveToFile() method stores the database metadata (AKA schema), > but not Delphi object's attributes (e.g. filter). It can also store the data > (and metadata) for nested queries (master-detail relation). > BTW, Oracle (and possibly other RDBMS) will readily load the XML created by > the above method (though the converse is not true without some minor > "massaging" of the output). That XML provides a convenient cross-platform > interface, and, though voluminous, is readily compressed by Zip or other > mechanism. > > > I have been using the TClientDataset "SaveToFile" and "LoadFromFile" > methods for a long > > time, but never realized that the file "FileName" > also holds the TClientDataset object > > structure along with the data. > Thank you, Robert. You opened my eyes. > > > Emmanuel > > > > > > > > > [Non-text portions of this message have been removed] >
