G
Guest
Much depends on how you plan to use the memo fields
later. Access has a major bug in exporting memo fields to
Word - they get truncated and scrambled if they get too
long. See Knowledge Base artcile 288877 for a discussion
of .rtf field truncation.
Other than that, Access likely will handle numerous memo
fields okay. They are content-searchable, just like any
other field, which is nice if you're searching for buried
text in a long memo entry. If you have "many" long memo
fields in a "great many" records, data base size might
become an issue long term.
You also need to think about how memo fields will be
displayed in forms and reports. The controls for
displaying them need to have growth properties set in
reports so they don't get chopped off. On forms you'll
get a scroll bar if the text spills out of the box.
If you have multiple users all hammering on the data base
at once, you'll want to think about using active record
locking so that the users don't keep tripping over each
other and making "changes to the changes" before anyone
knows what's happened.
Smart question for planning ahead! - good luck.
right db to use or should I use something else. Thanks
later. Access has a major bug in exporting memo fields to
Word - they get truncated and scrambled if they get too
long. See Knowledge Base artcile 288877 for a discussion
of .rtf field truncation.
Other than that, Access likely will handle numerous memo
fields okay. They are content-searchable, just like any
other field, which is nice if you're searching for buried
text in a long memo entry. If you have "many" long memo
fields in a "great many" records, data base size might
become an issue long term.
You also need to think about how memo fields will be
displayed in forms and reports. The controls for
displaying them need to have growth properties set in
reports so they don't get chopped off. On forms you'll
get a scroll bar if the text spills out of the box.
If you have multiple users all hammering on the data base
at once, you'll want to think about using active record
locking so that the users don't keep tripping over each
other and making "changes to the changes" before anyone
knows what's happened.
Smart question for planning ahead! - good luck.
which will be updated numerous times a day. Is access the
right db to use or should I use something else. Thanks