Question
October 11, 2007 at 02:16 AM
jobrown

Convert Access Database to SQL

by jobrown . Updated 18 years, 10 months ago

I have developed over the last couple of years an access database. As it stands at the moment it consists of the backend held on an unused PC with Windows XP Pro, which we use as our ‘server’ and I have 3 clients also on XP Pro. In addition there is a mass of mailmerge documents held on each of the client machines with their local datasource.

I recently set up a router with a VPN, I thought that I could map the remote drive, which I did and just use the linked table manager to connect. I guess you already know what happened next, egg timer and then nothing!

From what I have managed to find out so far my only option to make this work is to convert the backend to SQL. I have never used SQL and I am concerned that I would have problems making changes to the structure in the future.

I would also like to do away with the duplicated mail merge documents on each machine. It is a major pain if they need amending. We used to just have one set in the same folder as the backend, however we didn’t have access to the latest input information without closing the database and reopening.

Our entire business relys on this database and as it is growing it is becoming slower. So any ideas would be very welcome.

In case you haven’t gathered already I am completely self taught, so please give advice step by step, ‘idiots guide’!

This discussion is locked

All Comments