Limit on macros?

[jmj]

I use access to run bulk updates on 2 dozen db4 databases. Each site has it's own version of the db4 datbase so I write queries that go through each set of databases and run the updates. (In other words it's the same query that runs against 2 dozen different databases- the only difference is the table names have the site number tagged to the end -Demographics036, Demographics143 etc)
I use a combination of queries/macros/vb code to do this.

I then run the queries/vb code/macro from a macro.
ie: MacroUpdateTableA will list the 2 dozen queries to update tableA, MacroUpdateTableB will hold all the info to start the vb code running, etc.

So each round of queries is bundled in a macro.
I then made a "Master macro" so that I would only have to click one button vs running each macro separately. So this macro calls up each of the bundled macros.

I thought this would work fine. However, I had people come to say that some information wasn't updated even though I ran the Master Macro each day. Sure enough when I checked I noticed that the data from a month ago was still blank.
When I reran the one specific macro the fields were updated properly....
It made me wonder if I've tried to do too much in the macros. Are there limits on macros and how much can be nested in them?
Thanks,
J

 

[Crowley16]

hmm, I've not used macros that much, but it could be that there's an error in there somewhere which is stoping the update process in the middle but since you've used code + sql + macros the error message hasn't shown up...

--------------------
Procrastinate Now!

 

[jmj]

My Master Macro is literally just calling the other bundled macros
1.RunMacroA
2.RunMacroB
At the end of each macro I have it open a report. So if the macro doesn't finish the report wouldn't open. (or are you saying the error would just make it skip over without stopping) On the rare occassion that a site is down the program stops and gives an error telling me which site is down.

Lastly, each macro runs fine individually. They have been tested by themselves without a problem.

 

[JonFer]

Do you have any criteria for certain steps in the macro? If the result of a criteria is NULL, the macro stops without indicating anything.


John

http://www.interautomateconsulting.com

 

[jmj]

No I haven't added any stop points since it's just a bunch of if/then update queries.

The only time it stops is if a site is down. It'll then error out and say there's no connection.

 

[pbrodsky]

Just a thought. Have you tried converting the macros to VB, where you have a little more control? You might try that and see whether you get any error message when you run it.

 

[jmj]

The newer ones are in vb and I just have the macro call the vb code.

There are several that are macros that run sql code
and lastly one or two call a grouping of queries.
It made me wonder if there was a nesting issue....that the macro was jumping to the next event without completing all of the event.