[AccessD] ADO Save recordset format adPersistADTG

Hi Charlotte

Yes, as I understand it now, it's for storing a recordset (could be a table) definition and a snapshot of its data.
The ADTG format is compact and binary while the XML format is human readable but triples the file size.

The XML file stored this way is quite different from what you get if you use the normal "Export to XML" methods.

/gustav

>>> cfoust at infostatsystems.com 14-06-2006 23:18 >>>
No it wasn't.  The ADTG format was not XML, it emulated a Jet table.
XML was the human readable version.   


Charlotte

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Wednesday, June 14, 2006 1:59 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] ADO Save recordset format adPersistADTG

I dont know if this is still in general use but the human readable
version rather than binary can be seen using adPersistXML If you look it
has a self-contained XML schema along with the XML data. I think it was
brought in 1999 to help speed and was the first use of disconnected
recordsets and offline editing. I rember it causing a lot of confusion
with people using XML at the time. Because the resulting human readable
XML format was also called ADTG format.

 Advanced Data TableGram (ADTG)

Gustav Brock wrote:

>Hi all
>
>With ADO you can save a recordset to a file, normally an XML file, but
another format, Microsoft Advanced Data TableGram, exists:
>
>  rst.Save "d:\temp\records.dat", adPersistADTG
>
>Where or why could this binary format be used? 
>It creates file sizes about 1/3 of the XML file created if adPersistXML
had been used.
>Is it just a proprietary format for storing and retrieval of data
to/from a single external file?
>
>/gustav