A table that can accept unknow number of updates 2

[quig699]

Hi Guys,

I am looking for a way to set up a database to track customer issues. The wall I am running into is I want the users to be able to add notes that once entered can not be changed and the ability for the next user to add notes if needed. I am trying to create a sort of audit trail to track the customer's issues to resolution. Any thoughts how I would go about doing this?

Thanks

AMY =)

Thanks,

Amy

 

[SkipVought]

Hi,
[tt]
CustID NoteDatTim Note ResDatTim ResCD
[/tt]


Skip,
[sub]
When a group touring the Crest Toothpaste factory got caught in a large cooler, headlines read...
Tooth Company Freeze a Crowd! and
Many are Cold, but Few are Frozen![/sub]

 

[JerryKlmns]

Amy

If you create a form to input data and disallow Edit And Delete (form properties Data tab) then this is easy! Of course your users shouldn't be allowed to open the table or you should establish a user level security revoking permission to delete or updata data.

 

[sfatz]

Amy,
If each customer issue has a unique identifier, then why not create a separate table for the update notes. Each record of the note update table would have fields for Customer Issue ID, Date (and time if necessary), ID/Name of who entered the update, and of course, the Note itself.
To pull the information, use a 1-to-many query, where the two tables are linked on the issue id.
This has worked for me in the past.