Drew Wutka
DWUTKA at marlow.com
Mon Apr 7 14:02:38 CDT 2003
I completely agree that things are built to handle the current generation OS 'gaps'. Access doesn't care if it is reading from an NTFS or FAT. However, I was just hypothesizing that a future OS may have a file system that has capabilities that Access wouldn't know how to use, and they may have to make it incompatible with older software. (Such as File system indexing (of data)....so a db like Access could use the File Systems indexing....) Drew -----Original Message----- From: Marcus, Scott (GEAE, RHI Consulting) [mailto:scott.marcus at ae.ge.com] Sent: Friday, April 04, 2003 5:45 AM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] New Software releases Was: ADP vs Access mdb/SQL Drew, <<Software built for the current generation OS is going to be completely imcompatible. Why would you think this? I could see it possibly breaking some applications but for the most part, programs don't care how files are stored and retrieved by the OS. All programs care about are that the "black box" function calls they use still return the same answer. It matters not how that answer is achieved. Software that circumvents then OS to accomplish its job probably won't work, but API's are a layer that is supposed to hide the details. The whole idea of the OS(Windows OS that is) is to keep us from reinventing the wheel. I would say that changing the file access to SQL server is gonna be more of a concern to Executive Software, Norton, etc. not the Access developer. Scott _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com