From: Auntie Jack on 19 Mar 2010 03:46 Hi all, I am trying to link an Access Database to a SQLExpress 2008 database on my own machine. I can create a DSN that can see, and link to, the System databases (using Windows Authentication), but it can't see / connect to the database that I have created. Do I have to give myself specific permissions to my new database? Thanks - Ray
From: Andy B. on 19 Mar 2010 05:17 You're lucky. I can't even get Access to connect to sql server at all. I tried with Access XP and sql server 2008, but Access throws a canary and tells me only sql server 2000 databases or earlier are supported. I also tried using Access 2010 beta, but it doesn't even give me a choice for sql server 2008. It wants an ODBC provider but I don't have one. Any ideas? "Auntie Jack" <raycorbin1(a)gmail.com> wrote in message news:de023d8f-eb7c-48ed-adcd-07996d525574(a)33g2000yqj.googlegroups.com... > Hi all, I am trying to link an Access Database to a SQLExpress 2008 > database on my own machine. I can create a DSN that can see, and link > to, the System databases (using Windows Authentication), but it can't > see / connect to the database that I have created. Do I have to give > myself specific permissions to my new database? Thanks - Ray
From: Auntie Jack on 19 Mar 2010 06:24 Crikey! It's the opposite with me - I have an Access 2003 front end linking quite happily to a SQL Server 2008 db over a vpn, but when I try and link Access 2007 to SQLServer Express, both on my own laptop, no go. Perhaps you need to check your Jet or MDAC versions? When you create the new DSN, make sure that you specify (local)\SQLExpress as the Server to connect to. Jack
From: Auntie Jack on 19 Mar 2010 16:21 On 19 Mar, 10:24, Auntie Jack <raycorb...(a)gmail.com> wrote: > Crikey! It's the opposite with me - I have an Access 2003 front end > linking quite happily to a SQL Server 2008 db over a vpn, but when I > try and link Access 2007 to SQLServer Express, both on my own laptop, > no go. > > Perhaps you need to check your Jet or MDAC versions? When you create > the new DSN, make sure that you specify (local)\SQLExpress as the > Server to connect to. > Jack Solved it. Try this: Start / Microsoft SQL Server 2008 / Configuration Tools / SQL Server Configuration Manager Click on SQL Server Services Check which Services are running. If you have SQL Server \ SQLEXPRESS, that's fine. If you have another Service running (on mine it was SQL Server / MYMACHINENAME) then when you create the DSN, don't enter (local)\SQLExpress as the Server name. Instead, try (local) \MYMACHINENAME. For me (after a million experiments and some excellent suggestions on UtterAccess) it worked. Good luck to others. Jack
From: Andy B. on 20 Mar 2010 11:41 Mine keeps complaining about the server couldn't be found, doesn't exist or there is some other strange problem with the driver. Any other ideas? "Auntie Jack" <raycorbin1(a)gmail.com> wrote in message news:a40ed92e-e8e4-4e11-8d0a-9dbb10053e01(a)i25g2000yqm.googlegroups.com... > On 19 Mar, 10:24, Auntie Jack <raycorb...(a)gmail.com> wrote: >> Crikey! It's the opposite with me - I have an Access 2003 front end >> linking quite happily to a SQL Server 2008 db over a vpn, but when I >> try and link Access 2007 to SQLServer Express, both on my own laptop, >> no go. >> >> Perhaps you need to check your Jet or MDAC versions? When you create >> the new DSN, make sure that you specify (local)\SQLExpress as the >> Server to connect to. >> Jack > > Solved it. Try this: > Start / Microsoft SQL Server 2008 / Configuration Tools / SQL Server > Configuration Manager > > Click on SQL Server Services > > Check which Services are running. If you have SQL Server \ SQLEXPRESS, > that's fine. If you have another Service running (on mine it was SQL > Server / MYMACHINENAME) then when you create the DSN, don't enter > (local)\SQLExpress as the Server name. Instead, try (local) > \MYMACHINENAME. > For me (after a million experiments and some excellent suggestions on > UtterAccess) it worked. Good luck to others. Jack
|
Next
|
Last
Pages: 1 2 Prev: Calculate in SELECT Next: Server: Msg 207, Level 16, State 3, Procedure PROC_CLN_DATA, Line |