Too much data for Access - what are options?

[Cotswold]

SQLite is able to support moderate transaction rates. It is not designed to support the level of concurrent access provided by many client/server RDMS products. Most server systems provide table or row level locking without risk of data loss. Concurrency protection in SQLite depends on file locks to protect against data loss. Whilst it allows multiple database connections the whole SQLite database file must be exclusivly locked for amendments. As a result writes are serialised across all database connections, limiting the overall transaction rate.

But if you think you can get away with it then use it.

 

[cheekybuddha]

Whilst it allows multiple database connections the whole SQLite database file must be exclusivly locked for amendments

From sqlite:

... and no lock lasts for more than a few dozen milliseconds

What apps do you write where users require that kind of concurrency?

Anyway, I wasn't suggesting anyone should use SQLite (note I said caution should be used in a multi-user environment), just that your blanket statement was wrong.

 

[Neros]

You can run BULK INSERT on SQL Server to import .dat files to the database.
Or you can create a SQL Server Integration Services Package to run extract/transform/load and import data to SQL Server. Since Express edition doesn't support this feature, you can use Enterprise or Developer edition.