The import routines work well for most tables but development is still in progress. When importing data with SQLite Workshop, please keep these points in mind.

1. Excel imports are not complete. If you need to import an Excel spreadsheet, save the sheet as a comma-delimited file and import the comma delimited file.
2. The 'Map' feature is not yet implemented for imports from a database. This feature will allow you to map columns from source data to specific columns in your SQLite table or change the default column types created by SQLite,
3. Imports into existing tables are only supported if the existing table mirrors the data being imported and will only append rows. If you need the table emptied, TRUNCATE the table before importing new data.

BLOBs are not entirely supported. The Row Editor allows viewing BLOBs as pictures, text or hex. The grid editor will only show 'System.Byte[]'. Edits to BLOBs are not allowed. SQLite Workshop will import BLOBs and store them as SQLite BLOBs.

Encrypted databases are displayed correctly but editing tables and importing are not supported.

SQLite Workshop is English only at this time. I am looking for assistance to translate to other languages and to add localization.

All SQLite tables will contain a unique primary key unless you specify 'WITHOUT ROWID' and do not name a unique primary key when creating the table. If you do not name a unique primary key and do NOT include 'WITHOUT ROWID' when creating the table, SQLite will automatically create one for you - usually called 'rowid'. SQLite Workshop makes extensive use of this column and tables WITHOUT ROWID can be edited only if the changes would be applied to one and only one row. If you attempt to make a change to a row that would result in multiple rows being updated, SQLite will warn you and refuse to apply the update. This is true for row updates as well as row deletes.

This behavior is 'as designed' and cannot be modified.