Thanks Mike,

Sorry for my vagueness. I kind of took that as a given. I was only referring to the notes portion being in a memo field. I would have company info in a separate table, and a notes table with something like companyID,DateTime,Agent,Notes where Notes would be the memo field. I'm just not sure if my memo field concerns are justified or if I've run into a programmers urban myth. I'll try some tests and move on. Thanks again.

Marcus.

>Hi Marcus,
>
>>My first thought was to use memo fields to allow the support person to log in all the information. However, I've heard a lot of talk about memo bloat, which makes me think twice. Is this a situation where memo bloat might occur? Is it that severe of an issue?
>
>I don't think you should put all your info in memos, your table could be laid out like this:
>
>Company-C
>Phone-C
>Category-C
>SubCategory-C
>Handled By-C
>TimeStarted-T
>TimeStopped-T
>TimeBilledFor-T
>Billed-L
>Notes-M
>
>You should have a memo field for notes. But everything else could just be regrular fields. Just my opinion.