Exchanging data between ESdat users

Navigation:  Exports and Outputs > Data Exchange / Delivery >

Exchanging data between ESdat users

Previous pageReturn to chapter overviewNext page

Two methods are available to exchange data:  transfer the entire database; or use an ESdat Data Interchange File.

Transferring the entire database (typically an Access database) is appropriate when the database contains all the site data, and both users wish to use ESdat to look at the data using the same Access database.  Data stored in SQL Server databases can be automatically exported to Access databases.

Transferring an Access database may not be appropriate if the receiving party is wishing to import to a SQL Server database, in which case the EDIF may be more appropriate.


Transferring using an Access database

Users using Access versions can automatically zip the Access databases from ESdat by selecting File - Export - Zip Project. The receiving user unzips the compressed file using Windows Explorer and in ESdat selects File - Open - Other, and navigates to the file

Users using SQL Server can automatically export the data to an Access database by selecting File - Export - To Access.  The Access database can be opened in ESdat.


ESdat Data Interchange File (EDIF)

An EDIF is used to transfer of data from an Access/SQL Server database to another Access/SQL Server which contains data from multiple projects.  This format allows the new data to be integrated with the old.