Hi Scott,
Terminology first. ODBC isn't a kind of data store, it's a system for
connecting to any of a wide variety of data stores. XML isn't a data
store either, it's a markup language that can be used to describe the
structure of data in textfiles. SQL in this context means one of several
database servers that use SQL to define and query the data, e.g. SQL
Server and MySQL.
An Access application can use ODBC to get data from just about anywhere
(except from an Access mdb file, but that's obviously not a problem);
and just any ODBC-compliant application on a Windows platform can use
ODBC to connect to data in an Access database.
So your client's understanding could be even more "dangerous" than
yours<g>.
Are you selling him the data, or an application that uses it? If just
the data, there's no problem exporting Access data to XML, provided you
have Access 2002 (though the XML that Access creates may not be exactly
the flavour that your client's application demands). There's also no
problem exporting Access data into a format that a SQL database server
can import (if it's SQL Server, there are utilities to transfer data
more directly).
Converting an Access application to store its data in XML files or in a
SQL database rather than MDB files.is a different matter, however: from
hours to months of work depending the circs.
I need a little help. I am a sales type with a dangerous
understanding of some topics. I have a project where the
owner would like .xml, SQL or ODBC for database storage.
He wants to use the data for various energy calculations.
All my data is stored in Access .mdb files. Is the
conversion to one of the three listed a feasible and
economical thing to do?
John Nurick [Microsoft Access MVP]
Please respond in the newgroup and not by email.
