new to database set up 1

[action8]

We have a MS Access 2003 with only a single user on laptop.
We paid someone to do it. it worked ok, with minor bugs. They are hard to duplicate but we can live with them.

I read about front end back end stuff here. I can read VBA code but I am not interested in writing new code.
It has been a long time for me.

I also use MS Access 2007 and I think that most of you are right 2007 is a lot easier.

I love this type of forum, because I can ask questions and clarify the questions, better than any kind of book(s).

The big picture, now we want to move up to 2 or 3 computers that can access to the same database. The database is small.
5 tables, 3 queries, 5 forms, 3 reports and total data about 700 items (rows).
3 persons are in the same office about 1200sqft,
one person supervises who wants to know about the daily scheduling of workers.
one person daily enters time who show up, absent, get paid...and set up next week/month appointments
one person updates phone numbers, address of workers...
My plan:
one laptop as the master and the other pcs are slaves
reason: once a while, we just grab the laptop and go to work in the field with no network, just a stand alone laptop with the database on it. this happens probably two weeks every six months, also we can take the laptop home and work with the database for scheduling appointment or call reminder appointment...
if we split back end front end, do we have to connect to the network to connect to the backend every time?
I want a master and 2 slaves configuration, so I can work with the laptop once a while. If I create a backend, is that mean I lose the ability to be a standalone laptop?
just to be clarify I am not a student, don't want to be a student too old for punishment!!! sometimes my questions are similar, sound like students but no I am not a student.

 

[MaxieMax]

If you split out to a front end and back end... you will be able to access it on your laptop at any time if that is where both are stored. If you then put a front end onto the other two office PC's they will only be able to get access to the DB when the laptop is connected to the network. You will also have to open up the fire walls on the laptop to allow the PC users to connect to the DB.

 

[action8]

thank Maxiemax
when I split
will it ask for a network drive for the backend ?
how does it knows? on the laptop?
Later I have a question about autoexec.////

 

[MaxieMax]

when you split it there is more than one way of connecting to the backend. The most simple way would be to create links to the tables from the front end to the back end.... that way all your forms and reports etc will still work. If you have the backend on a network drive rather than the laptop you will then be able to simply put a copy of your front end on the other pc's and the links will work as long as the users have access to the folder on the network drive where you stored the backend.

If you keep the back end on your laptop then you will need to give the other pc's access to the folder on your laptop where you store the backend....depending on your setup you might find this a little more tricky... but if you manage it again linked tables will work better otherwise you will need to create a conection behind every form

 

[action8]

Thank MaxieMax
I read up about database corruption etc.. and
Kallal's article.
I have to concern with
1. firewall a little more tricky..
2. corruption of database over wireless network
3. standalone master.

with Sharepoint, solve my firewall issue, and database corruption

Can I put the back End on the Share point and also on the laptop?
may be just have to do a linked table manager whenever I want to use as a standalone system.

normally linked to SharePoint,
disconnect from Share point linked to local laptop
later reconnect to share point and relinked
will the data sync by themselves?

 

[action8]

hi MaxieMax,
Please,Can you tell me more about how to connect to laptop?