Andrew Lacey
andy at minstersystems.co.uk
Fri Jun 1 10:07:11 CDT 2012
Funnily enough it's where I got the original string from. But this "installable ISAM" error is stopping me Andy On 01 June 2012 at 15:35 Jim Lawrence <accessd at shaw.ca> wrote: > Hi Andrew: > > Check out this site/page for examples: http://www.connectionstrings.com/ > > Jim > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andrew Lacey > Sent: Friday, June 01, 2012 12:06 AM > To: Access Developers discussion and problem solving > Subject: [AccessD] OLEDB connection string > > Morning all > > > > I know I'm late to this but I'm trying to setup an OLEDB connection string > to > SQL Server. I've found info on the web for this but I'm not having any joy. > This > is a code snippet of what I have. > > > > strConnect = "Provider=SQLOLEDB;Data Source=FRGRAAPP02;Initial > Catalog=TALEG_CI;IntegratedSecurity=SSPI;" > > tdf.Connect = strConnect > > > > where tdf is defined as DAO.Tabledef and is sitting on a table definition of > a > table currently linked to an MDB. The code fails, however, with "Error > Attaching > tablename". Can anyone see what I'm doing wrong? The Data Source is the > server > name and TALEG_CI is the SQL Database which has no security on it. We're > wanting > to use Windows authentication. > > > > Help please. I really need this. > > > > > > > > Cheers > > > > Andy > -- > 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