Gentlemen,

I've discovered some interesting stuff. Previously, when I developed in Microsoft Access, I always used a front - end and a back - end. I did this by splitting the database. It works fine.

Actually, when you use VB, NEVER use database splitting. It slows down your application enormously. I use, for example, ADO in VB to access my database. I do this via an Access front - end. I open one connection to that front - end, and after opening the connection, I open about 20 recordsets. Normally, this shouldn't slow down the application heavily, because I use only one connection. But, under the hood, Access creates for every opened recordset a connection, I guess. That is slowing down the application very much. Starting the application, and opening 25 recordsets goes fast with one user, but when the second user access the database via a front - end, it takes more than 2 minutes before the user can make use of the application. The power of ADO is decreased when using front - end / back - end systems with Access databases. So, never do that.

For example, starting the application twice (with both applications accessing the same database, and it are the same programs) goes extremely more fast, because access don't hold connections (and thus resources), but your program does.

I hope this will help.

grtz