dbTalk Databases Forums  

Should I completely abandon Requery?

comp.databases.ms-access comp.databases.ms-access


Discuss Should I completely abandon Requery? in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Access Developer
 
Posts: n/a

Default Re: Should I completely abandon Requery? - 05-14-2010 , 08:54 PM






Well, perhaps unfortunately, David, data macros are the only way to create
Access Web Apps (SharePoint front ends), although they compile to "something
else", which we haven't had to deal with (except for the aborted DAPs). If
they can't convince us to abandon VBA, they can just not provide it for what
they think (and may be correct) will be the primary use of Access in the
future.

I guess I shouldn't complain... the first thirty-odd years of my computer
work, all the languages compiled or assembled to machine language or to an
intermediate language which later compiled to machine language. But much of
that time, it was possible, when necessary, to interpret the machine
language and patch it rather than going back to source and recompiling or
reassembling.

Larry

"David W. Fenton" <XXXusenet (AT) dfenton (DOT) com.invalid> wrote

Quote:
Banana <Banana (AT) Republic (DOT) com> wrote in
news:4BCA348B.4070507 (AT) Republic (DOT) com:

Now with 2010, I can see some use in using macros for simple tasks
and for data macros & web databases (where there's no choice
anyway) and I'm quite glad they enhanced the macro language - it's
not full bodied as VBA and I will continue to write more VBA than
macros but it's improvement nonetheless.

My concern with macros, even in their new guise, is managing them.
In VBA you can easily tell what's in use and what's not, because
it's compiled. That is, you can rename a function/sub, hit the
compile button and immediately know if it's redundant code that can
be removed. With macros, you can't do that.

Secondly, unless I haven't heard about it, there's no way to browse
through and search all macros and see what's interconnected.
Embedded macros were introduced in A2007 and they make it even
harder, in my opinion, to tell where things are happening.

So, troubleshooting seems to me like it would be very difficult.
Also, the main way I make my living is taking over old apps that
need revival, and very often this means figuring out a tangle of
spaghetti macros and rationalizing it into something more
manageable. If there has been no improvement in the tools for
maintaining and auditing macros, I, too, will avoid them for
anything where they are not essential (just like I do already).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.