[AccessD] VBA question

Ah... close, but 1-2-3's command language had an If... :)

There is no answer, it's just a big black hole! :)

Susan H.

> OK. I guess what I'm getting at is that a macro is basically automation of
the
> user interface. When you go beyond that, you are doing scripts or code. I
think
> that in Word and Excel, it's a macro while you are recording it, but the
actions
> are converted to code. It's no longer a macro at that point (even tho it
is
> still called a macro in Word and Excel). I could get into this deeper but
see no
> reason why. What is this for exactly?