T
TC
Jumping in briefly (cos I am at the outback races, & I haven't had time
to read the whole thread); so apologies if this has been said already:
* The Access development team is currently the largest that it has
ever been. (http://blogs.msdn.com.access)
* The Access team now owns their own copy of the database engine MS
Jet (which used to be owned by the SQL*Server team), and
* The Access group program manager has publically stated that "they
will not break DAO".
So IMHO, Access/Jet/DAO based solutions will continue to work, for as
long a there is a 32-bit Windows environment - be it native, like at
present - or emulated, eg. on future 64-bit hardware. That's gotta be
*at least* 10 years; maybe way more.
HTH,
TC (MVP Access)
http://tc2.atspace.com
to read the whole thread); so apologies if this has been said already:
* The Access development team is currently the largest that it has
ever been. (http://blogs.msdn.com.access)
* The Access team now owns their own copy of the database engine MS
Jet (which used to be owned by the SQL*Server team), and
* The Access group program manager has publically stated that "they
will not break DAO".
So IMHO, Access/Jet/DAO based solutions will continue to work, for as
long a there is a 32-bit Windows environment - be it native, like at
present - or emulated, eg. on future 64-bit hardware. That's gotta be
*at least* 10 years; maybe way more.
HTH,
TC (MVP Access)
http://tc2.atspace.com