Lona my copy came as part of Office Premier, not sure if it comes with Works or not.
Sandra, it's ODBC and yes you can use Access for that, below are the data formats Microsoft Access can export;
Application Version or format supported
Microsoft Access database 2.0, 7.0/95, 8.0/97, 9.0/2000
Microsoft Access project 2000
dBASE III, III+, IV, and 5
7 (Requires Borland Database Engine 4.x or later)
Paradox, Paradox for Windows 3.x, 4.x, and 5.0
8.0 (Requires Borland Database Engine 4.x or later)
Microsoft Excel 3.0, 4.0, 5.0, 7.0/95, 8.0/97, and 9.0/2000
Microsoft Word, Rich Text Format
Lotus 1-2-3 .wk1 and .wk3 formats
Delimited text files All character sets
Fixed-width text files All character sets
HTML and IDC/HTX 1.0 (if a list)
2.0, 3.x, 4.x (if a table or list)
Microsoft Active Server Pages
SQL tables, Microsoft Visual FoxPro, and programs and databases that support the ODBC protocol Visual FoxPro 3.0, 5.0, and 6.x
For an up-to-date list of supported ODBC drivers, see the Microsoft Knowledge Base.
ODBC data sources:
A data source is a source of data and the connection information needed to access that data. Examples of data sources are Microsoft Access, Microsoft SQL Server, Oracle RDBMS, a spreadsheet, and a text file. Examples of connection information include server location, database name, logon ID, password, and various ODBC driver options that describe how to connect to the data source.
In the ODBC architecture, an application (such as Access or a Microsoft Visual Basic program) connects to the ODBC Driver Manager, which in turn uses a specific ODBC driver (for example, Microsoft SQL ODBC driver) to connect to a data source (in this case, an SQL Server database). In Access, you use ODBC data sources to connect to data external to Access that do not have built-in drivers.
To connect to these data sources, you must do the following:
Install the appropriate ODBC driver on the computer that contains the data source.
Define a data source name (DSN) by using either the ODBC Data Source Administrator to store the connection information in the Windows registry or a DSN file, or a connect string in Visual Basic code to pass the connection information directly to the ODBC Driver Manager.
Machine data sources store connection information in the Windows Registry on a specific computer with a user-defined name. You can use machine data sources only on the computer they are defined on. There are two types of machine data sources ? user and system. User data sources can be used only by the current user and are visible only to that user. System data sources can be used by all users on a computer and are visible to all users on the computer and system-wide services, such as Microsoft Windows NT services. A machine data source is especially useful when you want to provide added security, because only users who are logged on can view a machine data source and it cannot be copied by a remote user to another computer.
File data sources (also called DSN files) store connection information in a text file, not the Windows Registry, and are generally more flexible to use than machine data sources. For example you can copy a file data source to any computer with the correct ODBC driver so that your application can rely on consistent and accurate connection information to all the computers it uses. Or you can place the file data source on a single server, share it between many computers on the network, and easily maintain the connection information in one location.
A file data source can also be unshareable. An unshareable file data source resides on a single computer and points to a machine data source. You can use unshareable file data sources to access existing machine data sources from file data sources.
Connect strings
If you are a programmer, you can define a formatted connect string in your Visual Basic code that specifies the connection information. Using a connect string avoids defining a machine or file DSN and passes the connection information directly to the ODBC Driver Manager. This is useful, for example, when you want to avoid requiring system administrators or users from first creating a DSN, or to simplify the installation of your application.
You can find more information about programming ODBC in the ODBC 3.0 Programmer's Reference Manual.
I hope that wasn't too confusing!
