ColumnHistory / AppendOnly

[Chip]

Hey Everyone..

I was wondering if anyone could help me program a button. I have a
Notes field, which is a Memo (with AppendOnly set to True). Its
helpful for me to record the date and time of comments in that
field.

I also have a tab for each record, that lists all the Comments in
chronological order. So the Record Source is set to the ColumnHistory
function. Works great..

What I want, is for there to be a "Submit" button if you will. I want
that button to Clear the Notes field, and update the ColumnHistory
field imemdiately. I've found that the ColumnHistory field sometimes
upward of several minutes to populate with the latest information. Is
there a way of speeding it up? If anyone could show me what event I
shoudl link that Submit button to and what parameter I should set,
would be awesome..

Chip Franklin

 

[John W. Vinson]

Hey Everyone..

I was wondering if anyone could help me program a button. I have a
Notes field, which is a Memo (with AppendOnly set to True). Its
helpful for me to record the date and time of comments in that
field.

I also have a tab for each record, that lists all the Comments in
chronological order. So the Record Source is set to the ColumnHistory
function. Works great..

What I want, is for there to be a "Submit" button if you will. I want
that button to Clear the Notes field, and update the ColumnHistory
field imemdiately. I've found that the ColumnHistory field sometimes
upward of several minutes to populate with the latest information. Is
there a way of speeding it up? If anyone could show me what event I
shoudl link that Submit button to and what parameter I should set,
would be awesome..

Chip Franklin

I would really suggest a different approach. You're storing a one (item,
whatever it is) to many (notes) relationship in a single field; worse, you're
storing two disparate pieces of information - a date and a note - in the same
field.

Much better would be to have a one to many relationship to a Notes table, with
three fields - a link to the primary key of your main table; a NoteDate,
default Now(); and a memo field for the note itself (a Text field if the notes
never individually exceed 255 bytes). You can use a Subform to display all the
notes in chronoligical order.

To clear the notes for an item, you would simply run a Delete query to delete
all the notes for that ID. The ColumnHistory feature need never come into play
at all.