Troubleshooting

Numeric single-column primary key — To keep the code manageable, Anonymize requires the primary key to be a single numeric or GUID column. If your database has a few tables that don't follow that pattern, they will be skipped during the Scan process.

AutoNumber and Identity columns — They are excluded from the Auto-Assign process. Typically updating these values is not allowed anyway and would break foreign key relations.

Lookup table not in the Lookup dropdown — Only tables added to the "Lookup Tables" form are listed in the Lookup converter's dropdown.

This converter is not compatible with the unique index on this column. — Converters have a property "Produces Unique Values" and that is not set for RandomNumber and other converters where that is not guaranteed.

Queries backed by Attachment columns — Access tables that contain an Attachment column are fully supported: schema scanning and Auto-Assign both work normally for all other columns in the table. The Attachment column itself is skipped, as it cannot be anonymized.

The limitation applies when a query is the selected source object and its underlying table contains an Attachment column. In that case, the Auto-Assign process cannot sample the query's data. This is an Access engine restriction: it refuses to read across databases (using an IN clause) from any table that contains an Attachment field, even when the Attachment column is not part of the query's SELECT list.

Affected queries are indicated with 'Unprocessable: attachment field' in the No Converter Reason column. Schema information is complete and converters can be assigned manually for all columns.