Hi Ray,
You were using the word "Macro" correctly as it applies to Access.
Many people use that word to mean VBA code in Access because that's
the term used in the other office applications.
For the reasons you were experiencing, among others, experienced
developers don't use macros. They use VBA. It is impossible to
single step or make any other use of the debugger when running Access
Macros. If you intend to develop in Access I recommend that you bite
the bullet and learn how to use VBA - sooner is better than later.
There is a tool to convert Access macros to VBA. Once that's done you
should use VBA exclusively except in those very few special cases
where you can't. You can do things with VBA that you can't with
macros.
HTH
--
-Larry-
--
"raymondp" <(E-Mail Removed)> wrote in message
news:47CCA5DA-0B99-4579-9204-(E-Mail Removed)...
> Thanks again for your help, but I figured out how to fill in the
values
> through a series of RunCommand macros.
>
> "raymondp" wrote:
>
> > I'm a novice user of Access, so I'm not sure what you mean by
single stepping
> > and I have no clue if the line in question is the one causing the
error.
> > What about creating a button that will copy the values from one
field into
> > other fields on the same form? Is this possible?
> > If you would like to debug what I'm doing, I can send you a copy
of the
> > database I'm working with. If you don't want to put your email
address on
> > this public site, you can send me an email at (E-Mail Removed).
> > I really appreciate the help you've given thus far. Thanks.
> >
> > -Ray
> >
> > "Larry Daugherty" wrote:
> >
> > > I haven't got a clue. If I had your stuff on my system I'd be
better
> > > able to analyze and debug it. Are you single stepping in the
> > > AfterUpdate event? Are you sure that the line in question is
the one
> > > causing the error?
> > >
> > > --
> > > -Larry-
> > > --
> > >
> >