reliability of the shared network approach?

[merlin777]

The microsoft website says the shared network folder method of sharing access is :
'Adequate for small groups with light data-editing'
What denotes a 'small group' and 'light data editing'?

I want to write a database for a local hospital department to record their patient appointments an print various timetables for staff and patients. At the moment they put their appointments in a shared outlook calendar then at the end of the week they read the appointments off outlook and handwrite timetables in word. There are about 10 of them and often leave outlook open on their pcs ready to add an appointment but they probably only do that a few times a day.

I tried doing this in excel but it all fell apart with excel's inability to do multiple simultaneous users. I was advised to look at access and all seemed well until I looked at sharing and read the above.

Do you guys think that with this size of group and level of data entry on a (NHS hospital) network this might be OK or should I be looking at a split front-end/back-end approach? I'm a complete beginner so the simpler approach the better!

 

[gemma-the-husky]

everyone here will say this

split the database into two
a) the data (tables)
b) everything else

link b to a. there is hardly any practical difference. It is easier to
1) back up the data in database a)
2) change functionality in database b)

you can develop and test b) against a copy of the data, then install a new version of database b) against the existing tables a) without any difficulty.

now although the application dbs (b) CAN be used by multiple users simultaneously, most people here would advise you not to do so. Give each user their own exclusive copy of the application database. Much much safer. Still multi user - it's the data that needs to be multi user, rather than the app.

Finally, try and avoid wireless connection to the tables in a).

 

[merlin777]

Thanks, Dave. That's a really useful reply.

After considering everything, this is my intended approach. Please leap in if you spot a problem...

1) learn access 2007 )

2) write the whole database at home on my laptop on access 2007 (I'll be using fake data because confidentiality will mean I can't see patient details)

3) I'll split into front end and back end databases

4) I'll give both files to my physio and she can put the b-e in a shared network folder (hard wired network) and give a copy of the f-e to all of her colleagues to put on their local hard drives.

5) Sit back and wait for the problem reports to roll in

6) fix them on my copy of the f-e on my laptop and give them an updated front end which can directly replace their old copies without affecting the b-e data.

That's the theory, anyway. I've just got to crack step 1 first!

The other issue I have to resolve is whether or not to give my physio an excel workbook which will load the appointments data from access and compile a number of different timetables for printing. She's the only one that will use it, probably just once a week.

The reasons for this is are a) I don't know access yet b) the timetables are heavily formatted and complex to produce and I know I can do that in excel but not sure about access.

 

[gemma-the-husky]

that sounds good

1) is the hard bit