[AccessD] Converting Customers to VB.Net

LOL.  Well, that is ok too I suppose.

I have to assume that MS listens to you where they don't listen to me or even Martin Reid?  Why 
don't you ask them to fix the damn bugs then.  Help us out here.

John W. Colby
www.ColbyConsulting.com


Jim Lawrence wrote:
> Sorry, but I may be reading this the wrong... but I am just rolling on the
> floor with your comments... you are making my day. ;-)
> 
> Jim 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Monday, June 29, 2009 7:50 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Converting Customers to VB.Net
> 
> Dan,
> 
>  >I think the reason we get upset with them is that they are the only choice
> we have, so we believe 
> that we are entitled to have a say
> 
> And I think the reason we are upset is that they CLAIM to be listening and
> then they polish their 
> toolbars.
> 
> Just come out and tell the developer community "We don't give a rat's ass
> about what you think is 
> important and we aren't going to support you.  MOVE TO .NET" and I think the
> response to them would 
> be entirely different.
> 
> Nobody likes to be jerked around year after year, promises made and broken
> year after year.
> 
> I think the developer community is jaded, we know that WE are of zero
> importance to Microsoft (in 
> the Access / Office universe).  And yet they (and their MVPs) consistently
> CLAIM otherwise.
> 
> There are a whole ton of people on this list who do some pretty powerful
> development work in Access 
> and yet to my knowledge nobody here has ever been asked for an opinion
> (other than perhaps a certain 
> MVP? who loooooooves the new product...) , nor have our opinions ever made
> one iota of positive 
> difference in the product.
> 
> Too busy polishing the friggin toolbars AFAICT.
> 
> When I develop an application for my client, THEY drive what I do for them.
> WE don't drive what 
> Microsoft does for Access, ergo WE are not the client.  Now if they would
> just quit TELLING us we 
> are the (or even A) client...  We clearly are not.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Dan Waters wrote:
>> Hi Shamil - 
>>
>> I agree with you on MS business model.  I think they've realized that to
>> plan for many years ahead to maintain two separate, but not that different
>> (VB.Net vs. VBA), programming methodologies isn't in their long-term
>> business interest.  Everyone should remember that MS has discontinued
>> issuing new licenses for VBA.
>>
>> MS is a profit-seeking company, so they will change as needed to get the
>> most they can.  I think the reason we get upset with them is that they are
>> the only choice we have, so we believe that we are entitled to have a say,
>> like we do with the government.  If MS was a smaller company, we'd just
> say,
>> "That's business!"
>>
>> Dan
>