Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

To Split or Not to Split? 1

Status
Not open for further replies.

spherey

Technical User
Jun 24, 2003
80
US
This is probably a pretty basic question, but I thought you all would be the ones to ask.

In what circumstance would you want to split your database into front-end/back-end? What is the advantage of doing this?

Also, is there something I can do which would still give the users read/update/insert permissions, but would prevent anyone from deleting the entire database accidentally?

Thanks,

Spherey
 
There's another thorough discussion of your question on the posts within the last 2 days. Have a look at that post and the helpful information.
Tom
 
For anything but the most trivial of databases I always split from the start.

Splitting benefits
[ul][li]Easier maintenance! User Interface is separate from the data.[/li]
[li]Easier for multi-user.[/li]
[li]Better performance with local FE. Have BE on server, FE on workstation.[/li]
[li]Issue FE as MDE/ADE. Stops 'accidental' modification of UI design.[/li]
[li]Simpler backup/restore. Data is self-contained and smaller than combined FE/BE DB.[/li]
[li]Easier to use data in other databases via linked tables e.g. for reporting[/li][ul]

Use the workgroup administrator to assign rights within the database (protect your workgroup file!) to remove delete rights.
 
Tom - Thanks, I'll do that.

Norris - Thanks, that's a big help. By workgroup administrator, do you mean the workgroup information file?
 
Tom - I found that other post you mentioned. Thanks for pointing that out.

I'm pretty clear on the advantages of splitting the db now, and I think that would be the best choice for this multiuser environment. Apart from my question re. how to keep the users from inadvertantly deleting the db (either the FE or the BE), my last question is this: what is the best sequence to follow, or does it matter? I mean, should I split the db and then run the user-level security wizard, or vice versa? And is it alright to password protect my VBA code, or could this be problematic?

Thanks a lot,

Spherey
 
Spherey
Afraid I can't answer that specific question. I haven't done anything in a multi-user environment, so don't know what sequence to follow.

Maybe you should post a new question. I'm sure someone can answer that quite readily.

Tom
 
Good call. I'll do that.
Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top