XML or Access DB/ADO Import/Export??
Mojo
As per a previous post that I've just done, to transfer data from one
VB6/Access DB app to another I created XML export files so that I could
export from one and then import into the other, but XML seems a really slow
method when files are only in the 1MB-3MB filesize bracket.
I'm just toying with the idea of exporting from one VB6/Access DB app to a
cut-down access db and use this cut-down db as my export file to import into
the other VB6/Access app - does this make sense? Would this be the
better/quicker way?
Thanks
mbyerley
just using a CSV file?
"Mojo" <ple...@dont.spam.com> wrote in message
news:7LadnSbK1I-VPxbQ...@brightview.co.uk...
ralph
wrote:
1) Use ADO Save method to pass a file in Advanced Data TableGram
(ADTG) format.
http://www.w3schools.com/ado/met_rs_save.asp
Read it back using ADO.Open <file>
2) Create a comma-delimited file (with a schema.ini) and pass that.
3) Use an ADO Stream. (But not enough information to know if that
would be a fit.)
4) OR ... Almost anything will be faster than XML. <g>
XML provides human-readable, self-describing, application and platform
independent, hierarchical data, that can also contain presentation
information. In that role it is superior to other DIFF formats
(defines more datatypes, for example).
However, IF you don't need that. Use something else.
-ralph
Mojo
Many thanks for the pointers. I just thought I had to use the XML route
because everybody seems to class it as the standard data transfer method -
but to me anything over a simple config file is too much for an xml doc!
"ralph" <nt_cons...@yahoo.net> wrote in message
news:299no6hbtjhcoh0pp...@4ax.com...
mbyerley
If the export isn't to a location outside his intranet, he should just
connect via ODBC to the other database(or establish a link table).
> -ralph
mbyerley
"mbyerley" <mDotByerley@VerizonDottieNettie> wrote in message
news:spWdnUOaooo8IhbQ...@giganews.com...
>
>> -ralph
>
>
Jason Keats
> I just thought I had to use the XML route because everybody seems to class
It's really only common if you're providing a (web) service which other
(not your own) applications will use.
Tony Toews
>VB6/Access DB app to another
If they are both your own app what do you care about folks seeing the
file. Use the method that is the easiest for you to code and debug.
Performance is almost secondary so long as it is reasonable.
>I'm just toying with the idea of exporting from one VB6/Access DB app to a
>cut-down access db and use this cut-down db as my export file to import into
>the other VB6/Access app - does this make sense? Would this be the
>better/quicker way?
That'd certainly be my prefernce but I'm an Access MVP so I have a
bias. <smile> That said if you have Access installed debugging the
table structure and data is exceedingly easy. Just click on the data
xfer MDB and view the data.
See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm. Creating an MDB file
and the tables required is very fast.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/