Bruen, Bruce
Bruce.Bruen at railcorp.nsw.gov.au
Mon Jul 25 19:10:29 CDT 2005
But beware! Some of the strings are specific to commercial offerings. For example, the postgreSQL string is for the CoreLabs PostgreSQLDirect .NET Data Provider. It is not for the vanilla odbc or OLEDB .net connections. bruce -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Tuesday, 26 July 2005 1:47 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Connection strings for ado Handy, isn't it. I fell over it a month or so ago too. Charlotte Foust -----Original Message----- From: John W. Colby [mailto:jwcolby at colbyconsulting.com] Sent: Sunday, July 24, 2005 6:55 AM To: 'Access Developers discussion and problem solving'; dba-vb at databaseadvisors.com Subject: [AccessD] Connection strings for ado I found this: http://www.connectionstrings.com/ John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -- 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 This e-mail and any attachments may contain confidential information that is intended solely for the use of the intended recipient and may be subject to copyright. If you receive this e-mail in error, please notify the sender immediately and delete the e-mail and its attachments from your system. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. Any opinion expressed in this e-mail and any attachments is not an opinion of RailCorp unless stated or apparent from its content. RailCorp is not responsible for any unauthorised alterations to this e-mail or any attachments. RailCorp will not incur any liability resulting directly or indirectly as a result of the recipient accessing any of the attached files that may contain a virus.