G
Guest
Looking for guideance on the most appropriate way to handle the following
scenario:
System: Team knowledge base
Phase II requirements: Users should be able to view data in the database
via queries etc. (this functionality already implemented); need a new feature
that allows the users to enter new items in the knowledge base. However,
these users should NOT have the option to edit other records (scroll through
records in the database). One suggestion I've received is to create a temp
table mirroring the main table where the newly added record would reside. On
the SUBMIT button, we would move the record from the temp table to the main
table and delete from the temp table. This seems a little convoluted to me,
so I'm requesting feedback for other options. Could you just handle this by
disabling the record scroll feature on the entry window? I guess the main
objective is the 'protect' the integrity of the data in the primary table.
Thanks in advance.
scenario:
System: Team knowledge base
Phase II requirements: Users should be able to view data in the database
via queries etc. (this functionality already implemented); need a new feature
that allows the users to enter new items in the knowledge base. However,
these users should NOT have the option to edit other records (scroll through
records in the database). One suggestion I've received is to create a temp
table mirroring the main table where the newly added record would reside. On
the SUBMIT button, we would move the record from the temp table to the main
table and delete from the temp table. This seems a little convoluted to me,
so I'm requesting feedback for other options. Could you just handle this by
disabling the record scroll feature on the entry window? I guess the main
objective is the 'protect' the integrity of the data in the primary table.
Thanks in advance.