[RESOLVED] help with splitting back end/front end

[dreamdelerium]

hey everyone, i have a question about splitting an access db into front end and back end. ive never done this before and just wanted to ask some questions. heres what im doing:

ive created a survey (7 forms, each form has about 3-5 tabs, each tab with 10-30 questions). the purpose of the tool is to collect all the date, prevent incorrect responses, and "clean" the data thats going to be stored. the peole filling out the survey's will have the hand written surveys and will input the responses into the db. there will be about 3-5 people doing this at any one time plus anyone should be able to access the project to view the data.

on a design level, i enter all the data and retrieve/display all the data using sql statements (ie, when the user click the save button it runs the docmd.runsql statement.) to store the data. how do i split the database and run an sql statement to store the data not in the local tables but on the server?
thanks for all your help
jason

[dreamdelerium]

oh, i should metion ive created the survey in microsoft access 2003. thanks

[Ecniv]

Create a new mdb - call it frontend.mdb
Create a new mdb - call it thetables.mdb


Ensure that the back end mdb is in the shared folder that all users have read write access to

Open the back end db
Import the tables

Open the front end db
import your code, queries, forms, reports
File> get external data > link tables
Pick the back end mdb, highlight all tables
Link

Runn your front end to confirm it all works.

Post back if not.

[Hack]

Your signature indicates you are using VB.NET, so why are you using Access for a front end?

Access should be doing absolutely nothing but holding your data. Everything else should be done via VB.NET

[dreamdelerium]

yeah, im doing a side project in access using vba (sorry, was on vacation. just saw the post)