Database structure

[stepone]

Hi all,

I've been creating a database for my wife's work over the last couple of weeks. I'm no access expert, but I am trying to help them out. This thing is going to be used in the real world, so I would like it to be pretty robust. Some comments by people in other threads I have started have led me to question some pretty basic stuff in my database design.

Basically, these people would like to be able to write their own reports, queries etc. after I've finished setting things up for them. Also there may be occasions when I want to make some changes to the forms etc. I have designed for them. So am I better to create 3 MDB files ;

1 - to hold the actual tables, nothing else.
2 - to hold my front end - tie this one up so they cannot change anything
3 - An empty DB for them to muck about with and create their own stuff

2 & 3 would be linked to the tables in 1.

This would seem to be a good way to keep things tidy.

Can someone please let me know if this is a good idea, and if not, perhaps suggest a suitable structure for what I want to do ?

Thanks,
Peter.

 

[Parker]

Hi all,

I've been creating a database for my wife's work over the last couple of weeks. I'm no access expert, but I am trying to help them out. This thing is going to be used in the real world, so I would like it to be pretty robust. Some comments by people in other threads I have started have led me to question some pretty basic stuff in my database design.

Basically, these people would like to be able to write their own reports, queries etc. after I've finished setting things up for them. Also there may be occasions when I want to make some changes to the forms etc. I have designed for them. So am I better to create 3 MDB files ;

1 - to hold the actual tables, nothing else.
2 - to hold my front end - tie this one up so they cannot change anything
3 - An empty DB for them to muck about with and create their own stuff

2 & 3 would be linked to the tables in 1.

This would seem to be a good way to keep things tidy.

Can someone please let me know if this is a good idea, and if not, perhaps suggest a suitable structure for what I want to do ?

Thanks,
Peter.

Wouldn't say that I would do that. Create a FE/BE tie up the front end and let them create their own reports and queries.