Well, having multiple back-ends would do the job for some months more, but like you said, this is not a permanent solution.

Well, I installed the SQL server and made the migration too. However, there are some problems with my source code: To open recordsets with DAO, I use Set rs = currentdb.OpenRecordset("test", dbOpenDynaset) which seems not to be ok with SQL server, since rs.FindFirst can't find anything. After some googling, I found out that I should change to: Set rs = currentdb.OpenRecordset("test", dbOpenDynaset, dbSeeChanges) so now i'm able to use rs.FindFirst, but i'm facing a new problem: Can't use rs.AddNew Any ideas? PS there are hundreds of thousands of code lines, so changing the way my software works is not an option. Like I said, I'm just trying to make things work as is.

Actually I meant SQL Server (Microsoft), not SQL Lite. :)

We use a legacy application (vb6 / access). The UI uses DAO to connect to the local front-end MDB file. Local tables are linked to the back-end mdb file which is located on the server. So far so well. The problem is that the back-end MDB is now 1,8 Gb and it will be 2 Gb pretty soon, which is fatal in MS-Access world. We're thinking of replacing the back-end db with sql server express, so we'll have to make minimal changes to the front-end databases (just the connection string). Is it a good idea? What is the correct procedure to import the back-end MDB to SQL server express? Which version (LocalDB etc) should we use? Thanks in advance. PS There is no option of making/buying a new application. We are trying to solve our problem with minimum effort.