its splitting time

[soundsfishy]

Ok ! im at the same where I have no choice but to split the DB to avoid data corruption. I made a copy to test it and used the wizard to it for me. I place the backend on the server which is our G:\ and the Front end the my C:\

When I place the Fe on my C:\ I was still able to view the data even though the table seem to be linked ok. My question is, can a user with a copy of the FE on his/her C:\ able view the tables or delete data in the table. I imagine that they shouldnt be able to.

Im not sure if Ive got the splitting of db under control.

Splitting to me seems like an easy process but Im juts not sure I have done it correctly.

 

[CustomCode]

Ok ! im at the same where I have no choice but to split the DB to avoid data corruption. I made a copy to test it and used the wizard to it for me. I place the backend on the server which is our G:\ and the Front end the my C:\

When I place the Fe on my C:\ I was still able to view the data even though the table seem to be linked ok. My question is, can a user with a copy of the FE on his/her C:\ able view the tables or delete data in the table. I imagine that they shouldnt be able to.

Im not sure if Ive got the splitting of db under control.

Splitting to me seems like an easy process but Im juts not sure I have done it correctly.

The safe method would be to place the backend of the database on a network drive and set the permissions.

Link the front - end, and DONOT specify the mapped drive letter path of the network drive. If you do... individuals who have specified a different drive letter will not access the database.

Use the following example:

The "\\IISShared\mystuff\" is my network path

Suppose your database is called My.mdb and the tables you want to link are called POs, WorkOrder and Invoice.

Put the following behind a command button.
When you are done, set the properties of the button (Visible to False)

DoCmd.TransferDatabase acLink, "Microsoft Access", "\\IISShared\mystuff\My.mdb", acTable, "POs", "POs", False

DoCmd.TransferDatabase acLink, "Microsoft Access", "\\IISShared\mystuff\My.mdb", acTable, "WorkOrder", "WorkOrder", False

DoCmd.TransferDatabase acLink, "Microsoft Access", "\\IISShared\mystuff\My.mdb", acTable, "Invoice", "Invoice", False

Good Luck Martin

 

[namliam]

Yep, Martin is right, using network UNC paths \\SomeNetwork\SomeFolder\SomeWhere is much better than using the local network mapping G:\

Go there...

Regards