Licensing options for this format begin with FME Professional Edition.
The Microsoft Access (JDBC) reader and writer modules provide FME with access to attribute data held in Microsoft Access database tables.
The performance of this format is dependent on the amount of memory allocated to the Java Virtual Machine (JVM). The following environment variables allow you to specify memory available to Java Plugins:
- FME_JVM_MIN_HEAP_SIZE: Initial heap size for initializing the JVM.
FME32_JVM_MIN_HEAP_SIZE: Same as FME_JVM_MIN_HEAP_SIZE, but applies to 32-bit FME Desktop on Windows, and takes precedence over FME_JVM_MIN_HEAP_SIZE.
- FME_JVM_MAX_HEAP_SIZE: Maximum heap size for initializing the JVM.
FME32_JVM_MAX_HEAP_SIZE: Same as FME_JVM_MAX_HEAP_SIZE, but applies to 32-bit FME Desktop on Windows, and takes precedence over FME_JVM_MAX_HEAP_SIZE.
These variables must be set for FME to honor them, and must be multiples of 1024K (for example, 4M and 64M, or 4096K and 32768K).
Note: To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.
Workbench Reader Overview
Click the Reader Parameters button and establish a Microsoft Access database connection.
Workbench Writer Overview
Click the Writer Parameters button and establish a Microsoft Access database connection.
The Microsoft SQL Server writer module stores attribute records into a live relational database. The Microsoft SQL Server writer provides the following capabilities:
- Transaction Support: The Microsoft SQL Server writer provides transaction support that eases the data loading process. Occasionally, a data load operation terminates prematurely due to data difficulties. The transaction support provides a mechanism for reloading corrected data without data loss or duplication.
- Table Creation: The Microsoft SQL Server writer uses the information within the workspace to automatically create database tables as needed.