Quote:
Question about this MDB file... Is it separated into a front-end and back-end database? If so, is it self-created or from a vendor?

Whoa... I have to be honest: I have no idea. My girlfriend created this database herself in access. I have to admit that I don't know what the difference is between a front-end or back-end database.
I'll ask her to be sure.

Quote:

I've had good success with using mysql as the backend database for MS Access apps. MySQL server will run on both windows and linux and is significantly more stable for a network environment than an Access mdb file. You then simply link the tables through odbc and you'll never know it's there.

This sounds very nice! So you're saying I should run MySQL (have heard about this, but don't really know what it is... again: ), and link the tables to that? Could you expain this a bit more please?
The way I was thinking to do it, was by simply putting this .MDB file onto the server, and giving access to it from the three different PC's. Since five people can work into one .MDB file at the same time, I didn't think this would be a problem.
What would then actually be the benefit of using mySQL?

Quote:

If you were to run MySQL or some other database of your choice, you could remotely connect to it through an SSH tunnel as opposed to a full VPN.

Again:
Seems I'm in for quite some fun. On the other hand, I also expect to learn a lot from it. So, here's one thing I can learn already...: what is the difference between those two?

Quote:

I had a similar situation for our reps when on the road. We have a customer database with an access front-end and mysql back-end. I wrote a little script that detects whether they are on the local network or not and if not, opens a ssh tunnel with putty and starts the database and automatically relinks the tables. Works great for our needs.