Storing Historical Notes

[tleoervin]

I have created a Call Tracking Database that I want to see the historical
comments in a different field.

I create a Comments field where text can be entered, I have also created a
Historical Notes field that is Enabled = No
Locked = No
I want the Historical Notes field to be Greyed out.

Here what I want to do...

I want the Comments field to always be blank, waiting for additional
information/Comments to be entered that will be housed in the Historical Data
field.

 

[mscertified]

It sounds like you need an additional table to hold just the comments, this
table would link back to the call table via the primary key of the call
table.
This would be a one (call) to many (comment) relationship.
You should have a date/time column in the comments table so you can sequence
the comments.
You can then display the comments on your form in a subform.
Presumably you want to disallow the updating of old comments but want to
allow entry of new comments. This should be easily achievable by setting
properties in the subform (allowadd et.)

-Dorian

 

[John Vinson]

I have created a Call Tracking Database that I want to see the historical
comments in a different field.

I create a Comments field where text can be entered, I have also created a
Historical Notes field that is Enabled = No
Locked = No
I want the Historical Notes field to be Greyed out.

Here what I want to do...

I want the Comments field to always be blank, waiting for additional
information/Comments to be entered that will be housed in the Historical Data
field.

Rather than a different FIELD, I'd really suggest a different TABLE -
related one to many to the call table. Each record would have a memo
field for a note, and a CallID foreign key to your main table. Perhaps
a NoteDateTime, default value Now(), would be helpful as well.

This will let you add as many notes as you wish, with a "new record"
always available to add a new note.

John W. Vinson[MVP]