Opens an ElevateDB session and database to use as the source for schema conversion and data migration.
Defines how EDB2MySQL connects to ElevateDB — embedded (local) or client-server (remote).
Once open, the session panel shows type, character set, and config folder or server address.
The session character set (ANSI or Unicode) determines which collation families are used during schema conversion.
Detected automatically from the open session.
Selects the EDB database to convert.
Once open, the database panel shows: name, size, and counts of tables, views, indexes, triggers, procedures and functions.
Lists all tables in the open database with row counts and encryption
status.
Used during data migration to track per-table progress.
Lists all EDB collations found in the database: collation name,
family, and number of columns using it.
The converter uses this to select MySQL/MariaDB collations and to
suggest a default charset and collation on the Target
Database tab.
No accented characters in CHAR/VARCHAR — enable this only when you are certain that every CHAR and VARCHAR column in the entire database contains only ASCII text (no accented or non-Latin characters). When enabled, columns in primary key and unique constraint positions are treated as accent-safe, allowing the collation map to prefer lighter accent-insensitive collations for those columns. If the data actually contains accented characters, enabling this option can cause unique constraint violations on the MySQL/MariaDB side.