True, Silky. All of the following is inherent in Bill McCarthy's 1-line post.
The MS Access product still exists in 2010, and the push to use a different data backend for MS Access long preceded the popularity of a 64-bit Windows. And the 32-bit ACE driver/provider replacement for Jet has been around for a few years now - and works on WOW64. As the CSS SQL Server Engineers' blog article pointed out, Office 2010 will be available in 64-bit, and a distributable 64-bit ACE driver/provider with it. Finally, there' a place for MS Access development, aside from creating a front-end with a real coding environment and language :-) ________________________________ Ian Thomas Victoria Park, Western Australia -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of silky Sent: Tuesday, 13 April 2010 3:35 PM To: ozDotNet Subject: Re: [OT] MSAccess developer wanted On Tue, Apr 13, 2010 at 5:24 PM, Arjang Assadi <[email protected]> wrote: > LOL, 64 bit jet engine, Apple should support Cuneiform on their tablets! > > With all due respect to original poster, this is not meant to be > having a go at anyone, please flame me if you wish, but I really have > to ask. > > Why wouldn't anyone use a VS2010 C# front end with (Sql Server > Express, ehhem sorry) Access Backend? Am I missing something? Have you > mentioned the idea to them? It can be argued that there are legitimate reasons to continue to use Access. It's not as simple as you may like to trivially replace it (it does things you've probably forgotten about). > Some (Development) tools are for UnDeveloping/UnderDevelopment. > > Kind Regards > > Arjang -- silky http://www.programmingbranch.com/
