There's no reason to store that computed value in your table. As fellow MVP
John Vinson likes to say "Storing derived data such as this in your table
accomplishes three things: it wastes disk space; it wastes time (almost any
calculation will be MUCH faster than a disk fetch); and most importantly, it
risks data corruption. If one of the underlying fields is subsequently
edited, you will have data in your table WHICH IS WRONG, and no automatic
way to detect that fact."
Create a query with a computed field in it that concatenates the two fields.
Use the query wherever you would otherwise use the table.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"rg" <(E-Mail Removed)> wrote in message
news:82D472ED-0B80-485D-9DA6-(E-Mail Removed)...
> Thanks for the information.
> I am trying to set the value of one field in a record based on the value
of
> two other fields in the same record. I created a macro that has one
action -
> SetValue. The Item is [Content standard]![ID], and Expression is [Content
> standard]![Strand ID] & "." & [Content standard]![Standard #]. I don't
> understand why Access thinks that my table name is an Automation object.
> There must be a better way to accomplish what I'm trying to do, any one
with
> ideas? Thanks,
> rg
>
> "Douglas J Steele" wrote:
>
> > Automation usually refers to using objects from another application
inside
> > your application. For example, you can use Automation from within Access
to
> > work with a Word document or an Excel spreadsheet.
> >
> > What are you trying to do in your code? Post the relevant code, and
indicate
> > where the error is occurring, and someone will probably be able to help
you.
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (no e-mails, please!)
> >
> >
>