Splitting a database

[Pure Salt]

I have never split a database before so could do with some help on the following please:-



1) Should all front ends be accdb files or should I change to accde?

2) If I need to create/amend forms or reports etc I presume I do this in the front end, do I then have to update everyone else's?

3) Can I set the front ends for everyone else to not be able to make changes to the design etc? If you can how do I do this?

Thanks

[NTC]

1) Should all front ends be accdb files or should I change to accde?
*** the accde format will 'lock' the FE so that a user cannot put a form/report into design view - whether or not that is appropriate is a matter of choice. In terms of core functionality - it does not matter and is not a requirement.

2) If I need to create/amend forms or reports etc I presume I do this in the front end, do I then have to update everyone else's?
*** yes

3) Can I set the front ends for everyone else to not be able to make changes to the design etc? If you can how do I do this?
*** accde

[Pure Salt]

Thank you.

Just to confirm - I could leave mine as accdb & set the others as accde. Then if I update mine I need to copy & paste over the others>

[Z1nkstar]

Yes you are correct when you have there front ends on there pcs you should then have a shared folder where you can update your database then you can tell them or setup a batch file that will copy the database from the shared folder.

[NTC]

you must maintain an accdb as the design master - - - and distribute the accde...... if you lose the accdb you are in real trouble as an accde cannot be reversed.....

[Pure Salt]

Ok, thanks.

[thebigthing313]

NTC pretty much covered everything, but there are two things worth noting, IMO:

In the course of designing your application, you may find yourself in situations where some workarounds use code that open a form or report in the background in Design view, hidden to the user. It's not common, but it does happen. If you find yourself using code that uses behind-the-scenes Design View type solutions, these won't work in ACCDE.

The other detail, which is more important, is that ACCDE requires good code. First, you can't create an ACCDE file if the database doesn't even compile due to syntax errors and what not. Also, proper error handling is crucial because in ACCDE, if your application encounters an unhandled error, the program just crashes. In ACCDB, you get that window that asks if you want to End, Debug... etc.

[Pure Salt]

Thanks

One last question (hopefully!!).

I've split the database & everyone is working fine. Need to make a small change so have take a copy of the accdb file, tried unlinking the tables so it doesn't update anything in the main database but every time I try I get 'Referential integrity cannot be enforced between linked tables & local table.