To macro or not to macro... 2

[straybullet]

... that is the question.

I have been given responsibility for an existing access 2K database which relies HEAVILY on macros - to the extent of using them to open each of 42 forms, run make table queries and to preview/print 72 reports (among other things).

Technically, it functions, albeit slowly. Should I recommend taking the time to revamp the database - doing away with it's macro dependence?



Let them hate - so long as they fear... Lucius Accius

 

[Ed2020]

If you're referring to Access macros (as opposed to VB "macros") then yes, do away with them. There are two valid places to use a macro in MS Access (in my opinion). Anywhere else you should be using VB.

Having said that your use of macros quite possibly has nothign to do with the running speeds of the database.

It really depends on what you're trying to achieve....

Ed Metcalfe.

Please do not feed the trolls.....

 

[mp9]

I agree with Ed, there are generally only two reason to use a macro - in my view these are Autoexec (read more here) and AutoKeys (read more here).

For basic advice on converting macros to VBA, check out

http://www22.brinkster.com/accessory/macros/004.shtml

and for some observations on converting old macro-based menu-/toolbars to "proper" toolbars see

http://www22.brinkster.com/accessory/macros/003.shtml

 

[Ed2020]

mp9,

Those were the two I was thinking of.

I would normally use a startup form rather than an AutoExec. I do find it useful to specify a startup macro (other than AutoExec) in the command line though....

Ed Metcalfe.

Please do not feed the trolls.....

 

[straybullet]

Thank you for confirming what I thought. Im going to start putting together a project scope.

Let them hate - so long as they fear... Lucius Accius