Haslett, Andrew
andrew.haslett at ilc.gov.au
Thu Mar 11 20:42:09 CST 2004
Forget about it!! I doubt anyone will be losing their job over it. Not the end of the world. -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com] Sent: Friday, 12 March 2004 3:16 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Arthur's article I erred and made a fool of myself in public. The really ironic part of it is that I'm developing an ADP in 2003 but shipping 2002-compatible code and I forgot that I'm using 2003. In short, I'm a fool and don't trust anything I say or write. Very sorry for this error, folks. Now I am totally aware of the meaning of the word "chagrined". I could try and foist some of the blame upon my brilliant editor at builder.com but that would compound my errors. It's not her fault that this slipped through. It's all upon me. Arthur -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steven W. Erbach Sent: Wednesday, March 10, 2004 6:32 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Arthur's article Arthur, While I haven't devoted much time to keeping up with SQL Server developments I do subscribe to a couple SQL Server newsletters: SQL Server Central and Builder.com. My eyes lit on the headline "Enhance Enterprise Manager with Access." I thought to myself I thought, "Self, isn't that what Arthur Fuller has recommended lo! these many eons?" I read through to the bottom of the article and, sure enough, there's your moniker. There was also the open question, "Why did Microsoft kill ADP files in Access 2003?" I remember some time back before Access 2003 came out you were biting your tongue in the groups here because you were under an NDA. The only thing I remember you saying was something about how disappointed you were with Microsoft's direction with Access. In Access 2003 are we reduced to using ADO in code to get at SQL Server data? I suppose that ODBC is still an option if one wants to have direct manipulation of SQL Server tables, right? Sorry if these are naive questions; I've been wandering for a while. Regards, Steve Erbach Scientific Marketing Neenah, WI 920-969-0504 Security and Virus information: http://www.swerbach.com/security/virusinfo.htm _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com IMPORTANT - PLEASE READ ******************** This email and any files transmitted with it are confidential and may contain information protected by law from disclosure. If you have received this message in error, please notify the sender immediately and delete this email from your system. No warranty is given that this email or files, if attached to this email, are free from computer viruses or other defects. They are provided on the basis the user assumes all responsibility for loss, damage or consequence resulting directly or indirectly from their use, whether caused by the negligence of the sender or not.