My First db Split-Help needed

[deere8585]

I have just finished my first ever database and will be installing it onto the companies computer network soon (hopefully),

There are a number of users at various work stations who will need simultaneous access to this db-

I have done some background reading into this already but most sites simply list the Tools-dbsplitter-follow steps of wizard approach & I don't quite think that this is all that is required to achieve what I want.

My understanding is this

1. Set up users with access rights & permissions
2. Follow the db splitter wizard-locating the "back end file" in a folder on the shared network.
3. This is then when I get a bit unsure of what to do next- I think in theory this should leave me we a "mydb_be.mdb" file that contains my tables as well as a secured.mdw file both located on the shared network & then a "mydb_fe.mdb" file located on my local drive- to then spred this to multi user function I should save a copy of my front end to a cd or "memory stick" & load it to each users machine, making sure that each copy of the front end is 'pointing' to the 1 back end.
4. I then get ever hazier in my certainty-do I then need to create a shortcut on each users desktop that locates their induvidual front end?

I had a mini test run with a test db I made & after step 2 I ended up with the back end located in a shared network file, no secured.mdw file that I could see & what I think is the front end on the desk top- is it as simple as making a copy of this and loading it onto another users machine? I feel I have missed something important here.

If anyone would be so kind as to show me where/if I'm going wrong I'd really appreciate it! Thanks in advance

 

[deere8585]

My 1st db split-Help needed please

I have just finished my first ever database and will be installing it onto the companies computer network soon (hopefully),

There are a number of users at various work stations who will need simultaneous access to this db-

I have done some background reading into this already but most sites simply list the Tools-dbsplitter-follow steps of wizard approach & I don't quite think that this is all that is required to achieve what I want.

My understanding is this

1. Set up users with access rights & permissions
2. Follow the db splitter wizard-locating the "back end file" in a folder on the shared network.
3. This is then when I get a bit unsure of what to do next- I think in theory this should leave me we a "mydb_be.mdb" file that contains my tables as well as a secured.mdw file both located on the shared network & then a "mydb_fe.mdb" file located on my local drive- to then spred this to multi user function I should save a copy of my front end to a cd or "memory stick" & load it to each users machine, making sure that each copy of the front end is 'pointing' to the 1 back end.
4. I then get ever hazier in my certainty-do I then need to create a shortcut on each users desktop that locates their induvidual front end?

I had a mini test run with a test db I made & after step 2 I ended up with the back end located in a shared network file, no secured.mdw file that I could see & what I think is the front end on the desk top- is it as simple as making a copy of this and loading it onto another users machine? I feel I have missed something important here.

If anyone would be so kind as to show me where/if I'm going wrong I'd really appreciate it! Thanks in advance

 

[GaryPanic]

ok - i might not be the best person to help - but have split some d/b up

the wizard works fine you should end up with 2 d/b -- Front end and Back end

shove the back end on to the server ( as near to the server drive letter as pssoble - don't bury it in too many sub folders )
so S drive / datebasefolder

now your front end should be sat on your local pc 9desk top ) now open this up and it should fall over - as you need to remap the tables use the tools/database utilise - link table manager follow the instructions - this is pretty clear it asks where the back is

now this is linked you can copy this link fe over on to the server and drop it on to the local pc's

i personally - make a folder on c drive drop it in there and then make short cut to it ...

then you are into printer problems - hopefully they all use the same printer -

 

[JCShort]

Instead of clicking on the path to link the backend tables in the wizard, I recommend typing in the UNC path name (\\servername\folder\db_be.mdb). Drive letters can change unexpectedly & will cause you real headaches.

I also make an MDE file out of the frontend and distribute that to the users. It compiles the DB & locks the code so nosey folks can't screw it up.

I STRONGLY recommend adding an auto-update feature to your front-end. Otherwise, manual updates are a nightmare. Redistributing to every user all the time is a pain. Especially if you're like me & forget to make 100% of the requested updates before redeploying