This is an online Microsoft Access database conversion tool to convert old and new Access database formats to SQLite database for now. It supports Access 97 and all versions 2000-2013-2019.
Depending on file size, the conversion might take a few moments!
After the Access file is uploaded and converted with no errors:
- the link to Web Database Application Builder will be emailed, which is using the sqlite3 data converted from Access instantly available on the Web! It is super easy and takes no time! If not interested at all in building the Application, please click on Export or use [CTRL+E] to download the zip file which contains the sqlite3 file. The converted sqlite3 database has a long name exactly the same as in the provided link. This is to increase safety and security for all downloads.
If interested in showing Access data on the Web:Please review the Migration Tips first. The Application Builder link will set the Database to "DB manual mode". This means your new database is safe from changing the structure, like incidentally deleting the table or similar. If you would like to continue migrating Access to Web with the help of Jam.py framework, import all tables into the "Test Import" Group. Click on Test Import/Import button, taking care of all needed DB fields correction or missing info. "Test Import" is just an "Group Item" for logically storing the tables. If keen, create your own Group Item, ie "My testing", or "Inventory", etc. Jam.py will create a dropdown menu if there is more than one "Group Item" with the tables in it. The Northwind Traders example from below might be a good start!
Access Personal Ledger template migration video - 5 minutes migration video
Video tutorial - Simple CRM built automatically with Selenium IDE in 2.45minutes, demonstrates the Tutorial. Part 1. First project
New style Demo - New style CSS Demo Application
Access Personal Ledger template migrated application - Migrated Personal Account Ledger
Access Northwind Traders template migrated application - Migrated Northwind Traders
After Importing some tables, just replace builder.html with index.html from the link to access your Application. Sometimes the index.html page will not show anything due to CloudFlare issues. Please try after some time. Or start over. One can even set the App password or create users within the Builder. The default App/Builder username/password is admin/111, change it on Project/Users and set Project/Parameters/Safe Mode to restrict access, etc. One can set all lookups to different tables as usual. It should be a fully functional App with all the bells and whistles!
It is important to note that once the Access file is converted and all tables Imported through the builder.html, it is not needed to use this service at all. Immediately use the Export [CTRL+E] option and download the Export file. Then, install the Python Jam.py framework locally or on the server, create the New application, Import the same downloaded file, and point the Application to sqlite database as per creating the New application. That is all.
This tool is for the database tables only, it does not convert MS Access file with no tables in it. Hence, no need to upload a Front End application, which probably connects to SQL Server or some other database(s). Output will be empty, or it will contain only a few tables. The ODBC linked tables are supported. Which means the tables will exist with no data.
The process is expecting that the Primary Key exists on all tables. The simple INTEGER is not a Primary Key. The Log File will indicate this. Please address and fix this issue before attempting the conversion. Only Use One Numeric Field as the Primary Key, ie. AutoNumber field.
MS Access might have a special character, space, slash/backslash, dash (-),quote('), etc for the table field, as well as table name. The conversion will try to replace those. However, we would advise to fix the issues in MS Access, before attempting the conversion.
The conversion will fail if there are linked tables in MS Access. Please remove any linked tables before attempting the conversion.
The conversion will fail if Access is using utf-16-li, no need to try again. No log or link will be produced and we suggest fixing Access.
There might be an #Error in the Access field, please fix it if conversion fails, and attempt again. The best is to inspect the Log file, sometimes clearly showing the error. If the log file is empty, something went wrong. No need to try again if Access wasn't fixed.
Please do not upload confidential, private or password protected/encrypted database. If conversion to SQLite3 is needed for such data, the tool can be provided on demand. Password protected database conversion might fail, no need to try again.
Terms and Conditions:
"This site and its components are offered for informational purposes only; this site shall not be responsible or liable for the accuracy, usefulness or availability of any information transmitted or made available via the site, and shall not be responsible or liable for any error or omissions in that information."Jam.py Team