Are there any issues with having many memo fields in a table.

[colezpapa]

I am going to be building an app that has a lot of inputs for long text fields. Lots of item details.
Maybe 15 fields that would be memo fields.
This database would have at most just a few thousand records, but with so many memo fields, will there be any issues to contend with? Speed wise, its fine.

 

[Crowley16]

apart from speed issues, there shouldn't be any problems...

--------------------
Procrastinate Now!

 

[colezpapa]

I remember a few years back with A '97, there was something with MEMO headers .....We used to see #DELETE in the memo field.

 

[dhookom]

Having a lot of any type of field whether they are Yes/No, Date, Memo, or whatever often suggests an un-normalized table structure.

I would expect your structure could be normalized to a related table with one memo field and a foreign key to your existing table.

I could be wrong ;-)

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[missinglinq]

I deal primarily with dbs associated with health care, and because of this my apps frequently have a large number of memo fields. I've never had a problem, but the secret to successfully using memo fields is to use them only for their intended purpose, which is to hold "memos" or notes. If there's any chance you'll need to do any type of manipulation with your data, it doesn't belong in a memo field! Many types of queries don't deal well with memo fields and often end up truncating them to 255 characters. Allen Browne has a great little article at the following site that explains the various problems with memo fields and queries and gives some workarounds for dealing with these problems.

http://allenbrowne.com/ser-63.html

Good Luck!

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!