Upgrading from access to SQL: Minor task or Major headache?

[Benjamin Bolduc]

Hi everyone!

The completion of our new office building is almost at hand! (Which means I finally get my own office!!). And with the new building comes an entirely new network that I get to design. I'm planning on replacing our peer to peer network with a client/server. This means, of course, that I'll be putting my Access MDB on a server instead of running it off my computer. The only problem with this is that I don't know what I'm doing (Shhh don't tell my boss).
Can I just put my MDB on the sever and share it much like I do now by putting it in my SharedDocs folder?
I'm getting the irking feeling that I'm going to have to upgrade to SQL server and even though there is a wizard in Access, I'm still nervous.
I have ALOT of complicated reports, queries, forms, code and macros in my DB. If I use the Upsizing Wizard, will I have to change any of them? Will it be difficult to create new objects or modify current ones? Will i have to learn a whole new program or coding language?
Can't things just stay the same?! ahem.... sorry

Anyway, If any of you kind, wonderful, and incredibly intelligent people could offer me some information, I'd most assuredly appreciate it.

Thank you!
Ben Bolduc

 

[edtab]

Just because you're moving your mdb to a dedicated server does not mean you have to move up to SQL.

What I suggest you do is "split" your database into a "front end" and a "back end" if you have not already done so. The back end should reside in the new server and the front ends should be installed in each work station which are then connected to the server.

I hope you have a "network person" to help you with this configuration since from experience, if the network connection is not done propertly, the work stations would lose connection to the server (your back end data) everytime they are shut down.

Hope this helps.


edtab