I am hearing that MS is starting to get away from macro usage and promoting more VBA usage. Anyone else hear anything about that. Macros seems to work very well for me. I would hate to see them fade away!

Macros in Access have pretty much faded away. Macros in Word and Excel are pretty much gone. No developer I know recommends using macros. VBA code is so much more flexible.

Hey Larry,

MS started to "get away from macro usage" in 97 - that's when the VBA editor was introduced I beleive. At the end of the day, you've got to go with what works well for you. If macros *do* disappear completely I reckon it won't be for a few years yet.

But I could be wrong, and it certainly wouldn't be the first time. Personally I hope I'm not as although I can code my way out of having to use macros there are certain circumstances when I think they are just invaluable!!

I think MS'll probably phase them out - possibly by removing support out of Excel first? Then seeing how that goes, then doing Access.

Just my $0.02...

Ad

I agree that VBA is better, but if a guy needs to get something up and running quickly, VBA is not the answer. New users don't always have 6 months or more to learn VBA enough to get a program running. Macros provide that quick and dirty way to let new users put something together.

Mornin' AD! I realize that the move away from macros started some time ago, but I have recently been informed that in the new "Access Bible", the chapter on macros has been removed. Too me, that is sad. Macros are very useful sometimes. BTW, I like the new updated/animated logo (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

Actually, in my opinion, the wizards provide most of the quick things a user might need to do. Frankly, if you understand the parameters of a macro, you should be able to understand the parameters of its VBA equivalent.

For example; creating a macro to open a form. The user selects the Openform Action, then fills int he parameters. How much more difficult is it to type DoCmd. then select OpenForm and fill in the parameters?

Your point is understood. Some of the things can be figured out pretty easily. The thing that I am talking about is the "whole"of vba to a new user. Such as public vs private, modules, classes, variables, procedures, etc. Those things can be very overwhelming to a person who is given a box of software by the boss and told to have something up and running next week!

You both raise very valid points. I think the move to VBA (and then the next level?) was inevitable, however there are some things that I think only macros can do - mind this is my limited knowledge here.

For example, I have two macros on my main db. One traps keystrokes and stops the function keys from being used. The other is my autoexec macro that performs a lot of critical tasks before the main menu is opened. I know you can also specify macros to run via the windows task scheduler - it's just a command line switch.

I COULD code these up. But why? The way they work now is perfectly adequate for the needs of my employer.

On the flipside, I can (and do) acheive so much more with VBA than I could ever do with macros. Heck, the current system I'm working on currently has approx 280 pages of coding to perform various functions - functions that are just not available if I were to set up macros for everything.

I think the current balance is about right. If you're only interested in setting up a basic db with no "advanced" features, then macros are the way to go. Otherwise, look into using VBA. Larry is right - it is more advanced, more confusing, and to be honest beyond the initial understanding of most people who only want something basic. It took me a long time to figure it all out. Basically it requires knowledge in the area, whereas macros are really simple to set up, by comparison!

Ad

PS. Thanks Larry... just a shame it's a bit squashed I need to shrink the gif slightly... (IMG:http://www.utteraccess.com/forum/style_emoticons/default/laugh.gif)

I don't disagree, but you can't do that in macros anyway! If the user needs to incorporate variables and classes, needs to deal with the concept of Scope, they have to learn VBA anyway. If they don't need to do those things, all they basically need is DoCmd.

So much can be done with Access that doesn't involve any coding at all. The command button wizard can take the new user a step further by automatically generating code they can then learn from if they want.

But 75% of programming involves If...Then...Else and Do While. If you understand those two looping concepts (For...Next comes under Do While) then you can do basic VBA structures.

I just don't like the idea of teaching people something that is obsolete. I'd rather start them with good habits.

Please don't get me wrong. I think VBA is great. Powerful, accurate, flexible, and most importantly can be used across the entire MS Office platform. I just hate to see that something as useful as macros has to disappear. I am trying to learn vba, but do not have enough dedicated time to get the job done effectively. An hour here, an hour there. Can't wait to be as good at it as you guys out there, doing it daily and on the fly off the top of your head. My hats off to you all. It was not an easy task to get there! Some day I'll get there, but I plan to retire in about 20 yrs. Hope I have enough time (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

Agree wholeheartedly. Don't want them to end up like me...using obsolete xlm macro language in Excel.

Howdy Larry,

you really do? (IMG:http://www.utteraccess.com/forum/style_emoticons/default/shocked.gif)

Do you know of any good web source on Excel4 Macros?

Honestly, no joke (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif) .

martin

Yep! Use it everyday. I had written some very large applications about 10-12 yrs ago that are still being used today. Any additions or updates are still done in xlm. No Martin, I do not know of any websites for xlm. I have looked several times, but I think the whole world has moved on (except for me), lol. (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

I am currently trying to move all the old xlm applications to Access, but time restrictions are preventing me from picking up vba as quickly as I need to. I'll get there someday!

XLM to Access VBA?

You have my deepest acknowledgement. I remember the ol' good times (just 10 years ago (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif) ) when I used XLM recorder to browse twenty files (as there was one sheet per workbook) and copy the data below each other into one workbook so that I could chart longer time periods. But, at row 16384, the fun was over (IMG:http://www.utteraccess.com/forum/style_emoticons/default/laugh.gif)

I never understood what the code's actually about. That's why the question about XLM source (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

All the best,
(IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)
Martin

Wow! I would think so! The " good old days" certainly had it's challenges along the way. (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

I think everyone should have to experience the old ways at least once so that they can truly appreciate the capabilities of todays technology. I will run and hide now as I expect the last statement could induce some violence! (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

I actually agree... lol

I only started using excel "seriously" in 95. VBA was around then, so I never ever ever ever used excel macros.

Doesn't mean I wouldn't like to learn though as you rightly said it's now obsolete!

Ad

Hello Larry,

you might be interested in another GET.CELL example here .

Vivat Excel4 Formulas! (IMG:http://www.utteraccess.com/forum/style_emoticons/default/frown.gif)

Martin