Question Split-Database. Keeping the front-end 'private'.

[BardiyaS]

Hi everyone,

I want to create a split-database. I want the entries made on the front-end to update into a combined table in the back-end.

Back-end: One table with everyones entry

Front-end: Multiple forms that feed into the back-end.

When person A accesses his front-end form, he can only see his entries.

When person B accesses his front-end form, he can only see his entries.

When manager A wants to look at the back-end, he can see everyones entry in one table.

 

[Galaxiom]

Each record would need to include a user field to record who made the entry. Then include the user value in the criteria for the queries. The manager has no criteria in their queries.

 

[BardiyaS]

This will only have tables and forms, no queries.

 

[Galaxiom]

You will need queries as your forms' Record Sources to achieve your goal.

 

[gemma-the-husky]

bardiyas

you cannot come to this with (apparently misguided) preconceptions.

in a database, the tables must be designed to store the data in an orderly manner (the term is normalised)

you interact with these tables through forms.

now in general a single table on its own is not a lot of use. the power of a database comes from joining two or more tables together in a query, which then acts like a table anyway.

so you most definitely do need queries