Jim Lawrence
accessd at shaw.ca
Sat Jul 16 13:24:03 CDT 2005
Hi Arthur: You have touched on one area where I have no knowledge...trying to connect a MySQL database without an ODBC driver or designing an ADP project for that matter. (I guess I should be reading your book?) Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Saturday, July 16, 2005 5:51 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Reporting field properties Well, with Oracle you have a point, but with MS-SQL, why on earth use ODBC when you can use an ADP project instead. Does not compute... save and except that you might need to support both platforms. But aside from all that, I simply found ADO to be much more understandable and intuitive than DAO. Arthur -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: July 16, 2005 2:18 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Reporting field properties On 15 Jul 2005 at 22:12, Jim Lawrence wrote: > Hi Stuart: > > I must say that agree with Arthur on this approach. The ADO connection layer > allows so much flexibility when writing Access applications. Most of my > clients initially started out with small applications but as they grew they > always moved to a MS SQL or Oracle backend. If I had written the program in > DAO it would have been a huge and expensive re-write. > You can still use DAO with SQL Server or Oracle. Just link to the backend using an ODBC SQL driver. -- Stuart -- 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