Splitting and multiple front ends

[thart21]

Need some advice on how to best handle this. I want to split my database and distribute to 6 users. Each user will have their own unique queries (due to the joins/criteria in each that are completely different) that are created off the same tables in the back-end, therefore, I'm thinking my only option is to create 6 distinct front-ends which will make automating any updates to forms, etc. cumbersome.

What type of performance issues, if any, might I encounter by doing it this way? If I create a single front-end, is there a way to hide queries that don't pertain to a particular user so they only see their own? There are 60 queries so we just want to keep it clean by allowing them to only see the 10 that are theirs.

Would appreciate any advice, thanks!



Toni

[boblarson]

I would not try to maintain multiple frontends. You can determine who is opening the database (especially if you have a table which stores their network login ID and which items they use). You can then assign different queries as the record source for forms or call different forms (I would look to make as much generic as possible and then assign the proper SQL when necessary for example).

[Bob Fitz]

Hi

You can hide a query. Right click the query and select "Properties". Tick the "Hidden" check box and click the Apply button.