I'm a bit concerned at what you're doing: it looks like this Notes
field is redundantly storing a bunch of redundant data, and that it
will keep getting bigger and bigger every time you select the combo
box. Are you perhaps using a Memo field where you should instead be
using a Subform based on a related table, with fields for the date,
the user code, and whatever field Combo235 represents?
John the form IS a MEMO field (so is Notes internal tracking)
No. The FORM is not a Field, nor is the Form a Table.
The Form is a *TOOL* - a window which lets you intract with data in a
table. Don't mix levels, even in your mind - it will lead to using the
program incorrectly because of your incorrect mental model!
what happens is the internal tracking notes are capturing the user's id
and the Notes memo field is what the customer will see (all the data
execpt the user's id)
what this is is a tracking feature for a shipping company. so we can
email our customers and let them know the status of their shipments (as
well as track other misc internal notes on the shipments)
Does the memo field cause a problem???
you see now why we need two memo fields (internal and customer
viewing).
If - as it appears - you are capturing multiple notes, each date and
time stamped, I would suggest that you in fact should NOT use a Memo
field.
Instead, use a Notes table related one to many to the shipment table.
It would be joined by the unique ShipmentID; there'd be a Date/Time
field defaulting to Now() to automatically capture the time that the
note was entered; and a Text or Memo field to enter *that individual
note*. The Notes table could also have a yes/no field indicating
whether the customer should see the note, or not.
You can easily generate an Email based on a Report showing *multiple
records* from this table - all the notes for that user.
Storing multiple ID's, dates, times, and notes in a single field is
NOT good design. Fields should be "atomic" - have only ONE value. Just
because you can store multiple disparate kinds of information and
multiple rows of text in a memo field does not mean that it's a good
idea!!!
John W. Vinson[MVP]