Embedded Macro’s

[Dick7Access]

I have been looking over a customer order db that the programmer doesn’t use any Embedded Macro’s. Everything is in VBA. I use Embedded Macro’s on all my cmdButtons. What is the advantage to not using Embedded Macro’s.

 

[Galaxiom]

I have never used a macro, only VBA. I would have to learn how to use macros so that is why I don't use them..

All the code is in one place. There are very few things in macros that can't be done in code but there are many things in code that macros can't do.

It would be a natural choice for developers who come from Excel or Word where their "macros" are all in VBA.

The Access optimisation wizard suggests converting all macros to code so I guess it is faster to process.

 

[pbaldy]

I also never use macros. Another advantage is better error handling (or error handling at all depending on version). The only exception would be if you were going to create a web db in 2010, where you can't use VBA.

 

[Mr. B]

I also have been totally using VBA for many years.

However, I am now developing in Access 2010 and find myself now using Macros. The reason for the big switch is that my client has a need for the database to be accessible by users in many parts of the world. They also want to take advantage of their SharePoint site. In order to provide the client with the best possible tool, I am developing this application as a Web Database. Therefore, I must use macros only. No VBA code is allowed.

This has been an interesting change and quite a learning curve, but I am finding that I can find ways to meet the need of the client just using macros in Access 2010. I might add that this includes macros attached to objects like buttons, etc in forms, Named macros that are not specifically linked to one object and Data Macros that are attached to a table.

So, the bottom line for me is, I think you are not so bad off since you have been using macros as you have a feel for using them. With that said, be aware that macros are completely different in Access 2010.

By the way, I still prefer VBA for stand alone or hybrid applications.

Just my two cents.

 

[Dick7Access]

I use a autokeys macro on ervery app I make to use F9 and F10 to go from datasheet view to form view. If I wanted to could that be done with VBA?

 

[Mr. B]

You can still use your AutoKeys macro when using VBA. You would not need to change anything about your macro.

 

[Dick7Access]

I started using autokeys when I first started computing and my first computor had MS works with a built in F9 as a single key toggle to go from datasheet view to form view. When I switch to Access (first ver.) I couldn't figure out how to make autokeys make a one key toggle so I use two keys F9 and F10, but thought that someday I would look up how to use VBA to make a one key toggle, but here it is twenty years later and never looked it up. Every time I have to make a db I say to busy now will look it up later. Has anybody ever made a one key toggle to go back and forth?