[AccessD] Access 2007 Question

"I think an Access 2010 app ported to the 'net stripped of VBA will be
mostly useless"

Hah! I think just about *any* MS Office product stripped of it's VBA
would be mostly useless - I mean, why would you pay for a tarted up
version of OO or similar?
Having the ability to make the software sing and dance with VBA is where
most the values lies IMHO.

Cheers
Darryl

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Tuesday, 27 October 2009 7:58 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 Question

> Now, when an Access 2010 application is published to the web, it gets 
> converted to stuff like HTML and Javascript and SharePoint workflows.

> How you going to do that with VBA?
> Macros, based on XML, is going to work - VBA is not.  Simple as that.

Steve - I don't quite understand the above.
Why can't they translate much of the VBA by creating a Javascript
library of functions and objects and then create a translator to convert
the VBA code to Javascript ?
They were able to translate VB6 to VB.NET, so why not VBA to Javascript
and/or their new highly touted XAML ?

I think an Access 2010 app ported to the 'net stripped of VBA will be
mostly useless.

"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential,  may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."