[AccessD] : Re: Demise of VBA

DWUTKA at marlow.com DWUTKA at marlow.com
Thu Jul 13 16:30:07 CDT 2006


I think it's a developer thing.  We use the Access object model so much that
it's second nature to us, yet the Excel and Word object models seem so
awkward sometimes.  I can do tons of stuff in Excel, but I avoid Word VBA
when not absolutely necessary.

Drew

-----Original Message-----
From: Charlotte Foust [mailto:cfoust at infostatsystems.com] 
Sent: Thursday, July 13, 2006 3:45 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] : Re: Demise of VBA

The switch to VBA in Excel was hell!  I never did get back to my
previous level of proficiency in programming Excel with they switched to
Vba, and I too abandoned it.  AccessBasic and VBA were very similar,
which wasn't the case with WordBasic and VBA.


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Thursday, July 13, 2006 1:39 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] : Re: Demise of VBA

I found the switch from Excel Basic to VBA difficult. Now, Access Basic
and VBA were like peas in a pod, but Excel? I never have gotten the hang
of using VBA in Excel and I've pretty much stopped trying. 

Susan H. 

Dropped because nobody was (really) using them....
Not to my knowledge anyway

If the migration learning curve is low like 0.something like from Word
or Access basic to VBA and the code can be reused I dont see that as a
drop, but as an upgrade...


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list