Right now, Access is not quite sufficiently object-based/object-oriented to make this mesh with .NET, IMO.
There's so many things that falls short of being OOP. It bears to remember that Access wasn't really designed for programmers but rather information workers who wanted manage their data a bit more efficiently.
I'd rather that Access team work more on 1) making the objects in Access act like an actual object, 2) re-work the interface so there's implicit encouragement for users to develop good programming habits to make it a truly more scalable product and thus can transition into a OOP environment easier.
But that's just my 2 cents, before adjusting for inflation.
PS: I vaguely recall a blurb that it was originally slanted to be .NET-enabled for 2007 but was dropped due to too much work needed to be done in doing so. Also, I recall a usenet thread indicating that Access form did not in fact inherit from Windows form; rather using their custom form, which behaves just a little differently from the rest of Window forms and thus needs to be reconciled, especially that Access forms are far more data-centric and has multitudes of events to support validation, data handling, and what have yous, all automagically while doing it in .NET would be a long & tedious manual work.
