storing calc/concat of a text box on a form

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Although I hear over and over that it is not recommended, I really need to
store the beginning portion of last name, first name, company name fields for
future use in report generation and queries. Currently correct info is
displayed in an unbound text and I have a field defined in the table for this
info but have been unable to get the table update.
 
Why do you need to store it? If you can calculate it in an unbound text
box, then you can repeat that process in your reports.

Your example would not be a case where you'd need to store a calculated
value.

Post more details if you disagree.
 
FYI, what if a person's name changes (married, divorced, etc.) What if the
company changes their name? Are you going to remember to update that
calculated field in all these instances?
 
Hey Thanks for your input!
with regards to the change issue - all table fields should update on change,
the text box currently updates appropriately on name edits.

with regards to the storing issue - I want to store the info for sorting
purposes, like using the name to create a contact account "number' that will
maintain alpha order (there is already a key field that maintains related
tables) This DB is being created for a small non-profit organization and the
person who will be utilizing it has only basic query/reporting skills.
 
"all table fields should update on change" - well, Access does not have that
functionality at the table level. That is why you don't store a combined
field like that.

"for sorting purposes" - either use multiple fields in your "sorting and
grouping" options for the forms and reports, or create the combined field on
the fly (in your query) and then sort off of it.

"like using the name to create a contact account "number' that will maintain
alpha order" - How can you do that? What if You create a record (A0001)
for Adams Automotive and then (A0002) for Alfred's Car Care. What happens
if you later add a new vendor (Adamson's parts house)? If you want to sort
by name, then sort by name; don't worry about the person's identification
number. They are two separate things. To try to make your customer number
a sort when you already have a name field would be a maintenance nightmare.

"person who will be utilizing it has only basic query/reporting skills" -
Then by all means don't do strange things here!! Use normalized designs and
don't stray from the usual recommendations that you find in the newsgroups.
How will that person ever get help down the road if they have a "funky"
design?

Good luck,
 
Back
Top