Jim Dettman
jimdettman at earthlink.net
Mon Feb 9 06:38:57 CST 2004
Although Ken certainly has the inside soup, it certainly sounds like a lot of conjecture on his part about where Access might be going. The file system changes makes a lot of sense, as we all know database container corruption is the #1 problems with Access/JET, and JET is certainly on its way out. As for the rest, I really don't know. Yes, .Net is not going away, but it is not going anywhere real fast either at the moment (contrary to what Microsoft would like you to believe). For most, it has been a yawn at best from what I've seen. The learning curve is quite steep and developers are just plain tired of switching gears every few years. Look how many of us still use Access 97 or 2000. I think we need to move a little more into the future before we'll have a semi-firm idea of where it's heading. Anything at this point is just idle speculation. Jim Dettman President, Online Computer Services of WNY, Inc. (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of MartyConnelly Sent: Sunday, February 08, 2004 6:15 PM To: Access Developers discussion and problem solving Subject: [AccessD] Next Version of Access 12 Musings on what might happen Thought this might be of interest. What's Next? Microsoft hints at what the future might hold for Access. By Ken Getz http://accessvbsql.advisor.com/doc/13516 -- Marty Connelly Victoria, B.C. Canada _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com