Most of the code in both classes is duplicated

Ensure to free the Interop when closing

Use profiles for each database with the below info:

• Database file
• Working copy folder
• Import/Export options
• Last export datetime
• other...

The profile can be saved with .accvcs extension associated to MSAccess-VCS application. Also, usual mdb, accdb... extensions can be associated with MSAccess-VCS to allow the command "Open with..."

Maintain in the application a MRU list of profiles

From the Spec collection: CurrentProject.ImportExportSpecifications

Error from DAO Index already exits while relations are created from file

This feature would allow automatic export of all modified objects

• It could be integrated in an Access Add-in, and export modified objects when exiting from Access
• This could allow to preset the objects to export in the standalone GUI
• Add a flag in the command line tool

NOTE: Needed to compare with existing files to detect removed objects

This options could include:

ExportOptions:

• Clear folder structure before export [Default: true] In this way source code management tool will detect removed objects from Access database
• Export queries as SQL [Default: false] By default queries are exported by Access.Interop. This could be a flag enum to allow to export in default format, sql, or both
• Export table data
• Use custom file extensions: By default all generated files have .txt extension. But external editors can take advantage of different file extensions for syntax hightlight
• LogLevel and LogFile

Default behaviour is replace all relations with new ones.
Add an option to choose between

• To keep existing relations and add the imported relations
• To remove existing relations and add the imported relations