[AccessD] Demise of VBA

I happen to agree with ya William (did anyone else see the sun eclipse?)!

Drew

-----Original Message-----
From: William Hindman [mailto:wdhindman at dejpolsystems.com] 
Sent: Tuesday, July 11, 2006 10:04 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Demise of VBA

...Office is the goose that laid the golden egg for MS ...its what keeps 
Windows the dominant OS on the desktop and the gold flowing into the MS 
coffers.

...VBA is NOT like Word Basic or Access Basic in that it has become the 
unifying structure for the entire Office product line ...and thus replacing 
it with VS.Net would be like replacing Coca Cola Classic with new Coke 
...the masses that feed the golden goose would rebel

...Access 2007 divorces itself from the old workgroup security model which 
addresses most of the security issues with prior versions ...it also has 
finally removed the Access Jet db engine from the Windows/SQL Server 
development teams and given the Access development team free rein to make an

adb work as it should for its target audience.

...what I've seen of 2007 so far gives every indication that the Dao model 
is back in the saddle ...that would appear to indicate that no ado centric 
language will be replacing VBA anytime soon.

...while SQL Server Express certainly lowers the bar to an Access type rad 
fe tool that would not require vba, the underlying fact is that vba is 
common to one hell of a lot of widely used Office applications that are not 
going to give it up as readily as Access might ...and thus I would believe 
the imminent demise of vba is greatly exaggerated.

...just my opinion of course.

William

----- Original Message ----- 
From: "Kenneth Ismert" <kismert at sbcglobal.net>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, July 11, 2006 1:43 PM
Subject: Re: [AccessD] Demise of VBA


>
> VBA is a dead language -- I've been saying that for a while now. When
> Microsoft stops updating a product, it's only a matter of time before
> it sunsets it.
>
> There are two driving reasons for this shift, as I see it:
>
> * VB6 and VBA have deep security issues. Microsoft is unwilling or
> unable to address this.
>
> * The VBA environment was included in Office, and Microsoft wants to
> realize extra revenue from the sale of VSTO.
>
> What does this mean for us?
>
> * Vastly more expensive entry into development. Very likely, VSTO will
> require a full version of Visual Studio -- no Express edition here.
>
> * Vastly higher learning curve. You thought the current system was
> tough? Try wrapping your head around a new language (don't believe the
> bullshit that VB.NET is any easier to move to than C#), new IDE,
> enormous new libraries (ADO.NET, BCL), and completely new
> methodologies. Not to mention the radically new Access 2007 interface.
>
> My point is, if you have to re-learn everything, why limit yourself to
> just Visual Studio? There is a universe of languages and development
> evironments, all free, for you to explore. And, not crippled intro
> product -- full-featured and free.
>
> You really owe it to yourself to explore the alternatives.
>
> -Ken
> -- 
> 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