[AccessD] F'n 2007

Then it should be in the base language, not in the extensions.  The interfact should exist in the 
base language and each application should work to the interface.

The problem is similar to buying a company and trying to merge their existing databases.  It is 
never trivial.  Pretty much all of the office applications were purchased from some third party and 
"merged" into an "office" environment.

John W. Colby
www.ColbyConsulting.com


Mark Simms wrote:
> Just very quickly I am coming up with...
> 1) the handling of the STATUS BAR
> 2) adding items to a list box
> 
> I'll bet we can come up with dozens more that should have been made common.
> 
> Add Powerpoint and Outlook to the mix...and the list probably goes into the
> hundreds of items.
> 
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>> Sent: Monday, July 27, 2009 10:35 AM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] F'n 2007
>>
>> LOL, it is entirely likely that they in fact never did
>> collaborate at all.
>>
>> VBA is a base language.  VBA for Access simply adds
>> extensions required to understand Jet and Access specific
>> things.  VBA for Excel simply adds extensions to understand
>> excel specific things.  What the Access team would add to
>> Excel's team when writing Excel extensions is pretty
>> questionable, and vice versa.
>>
>> John W. Colby
>> www.ColbyConsulting.com
>>
>>
> 
> 
>