G
Guest
This arises from the unhelpful way in which Access runs queries and macros -
the status line says something like 'Processing query' with a time bar, but
does not say which query!
I got fed up with this over-discrete approach and in a few cases have
stuffed the actions (eg action type, object name) of macros into a table - a
prcedure ploughs through the table and reports the action being performed and
the numbers of records affected. All very nice, but why not process the
original macro to do the same thing?
I have more than a sneaking suspicion that an Access macro is actually a
table, with columns for action, objectid, comments etc. Any ideas?
Ys H
Programming is a hobby!
the status line says something like 'Processing query' with a time bar, but
does not say which query!
I got fed up with this over-discrete approach and in a few cases have
stuffed the actions (eg action type, object name) of macros into a table - a
prcedure ploughs through the table and reports the action being performed and
the numbers of records affected. All very nice, but why not process the
original macro to do the same thing?
I have more than a sneaking suspicion that an Access macro is actually a
table, with columns for action, objectid, comments etc. Any ideas?
Ys H
Programming is a hobby!