DWUTKA at marlow.com
DWUTKA at marlow.com
Thu Feb 12 13:48:16 CST 2004
Actually never used them, just knew they were there. Have only ever used AXP once. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Thursday, February 12, 2004 11:35 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Next Version of Access 12 Musings on what might ha ppen (RANT) Personally, Drew, I've had problems with the printer object in 2002, so I still use the API calls, which are totally reliable in any of the versions. Charlotte Foust -----Original Message----- From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] Sent: Thursday, February 12, 2004 9:19 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Next Version of Access 12 Musings on what might ha ppen (RANT) I see. Just don't confuse refusal to change, with no motivation to change. For instance, I have finally started developing A2k dbs, for both personal and professional stuff. The ONLY reason I did this, is because A2k's VBA allows for stuff not available in Access 97. (event stuff). Other then that one particular issue, there is nothing I actually need in later versions, that Access 97 doesn't already provide. It is really a matter of scope, though. For example, AXP came with a printer(s) object, which blows away dealing with printers from early versions. However, I have only ever had to deal with a printer at that level once, and it wasn't even from Access, it was from VB. So even though there is a new feature, it isn't really something I need in the projects I build. If Microsoft really wanted to upgrade the world, they need to come out with something that just can't be matched by previous versions. Not just glitz and glitter, or a new feature here or there. They need to improve the core processes. As far as .Net goes, I like VB 6. I don't refuse to move to .Net, I just frankly don't have the money to purchase it, and VB does what I have needed it to do, to date. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Haslett, Andrew Sent: Wednesday, February 11, 2004 5:15 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Next Version of Access 12 Musings on what might ha ppen (RANT) Completely. My 'refuse to accept change' was more aimed at us developers, rather than a compulsory upgrade of OS / App software by Organisations at every release. Cheers, A _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com