It's usually not so hard because the same questions come back when you have
a new installation. However, you don't give us any detail about your
installation, what you already know about SQL-Server, what you try, etc.; so
unless someone here is willing to write a whole chapter on the subject in
the hope of hitting your problem by chance, there is not much to say.
--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)
"csufsu" <(E-Mail Removed)> wrote in message
news:00AE3958-C059-4742-8F1B-(E-Mail Removed)...
> Thanks for giving me some direction. The learning curve on SQL server
> seems
> to be rather steep - lots of parameters to deal with.
>
> "Sylvain Lafontaine" wrote:
>
>> Well, you don't tell us how you are trying to connect to this server so
>> it's
>> hard to give you an answer on this. A more appropriate newsgroup such as
>> microsoft.public.sqlserver.connect or m.p.sqlserver.server would be more
>> appropriate than this one.
>>
>> In your case, we must know if your installation of SQL-Server 2008 is the
>> default instance or a named instance. We also must know if the tcp/ip
>> and/or the named pipe protocols are disabled (they are by default with a
>> new
>> installation of SQL-Server 2008 if I remember correctly); so what remains
>> is
>> the shared memory protocol. We must also know if the sql-server
>> authentification is activated or if it's only the windows
>> authentification
>> that you can use to connect to it and if so, is any built-in
>> administrator
>> account activated on the sql-server. Also notice that the fact that an
>> admisnistror account exists on the target desn't mean that this account
>> has
>> been activated on the sql-server itself for login purpose.
>>
>> You have created a small database, so you can connect to the SQL-Server
>> 2008
>> using a client tool such as SQL-Server Management Studio Express
>> (SSMS-E); I
>> would suggest that you use the same parameters to connect to your
>> database
>> using the DSN driver.
>>
>> Try reviewing the tutorial in Books Online:
>> http://msdn.microsoft.com/en-us/library/ms345343(SQL.90).aspx
>>
>> --
>> Sylvain Lafontaine, ing.
>> MVP - Windows Live Platform
>> Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam
>> please)
>> Independent consultant and remote programming for Access and SQL-Server
>> (French)
>>
>>
>> "csufsu" <(E-Mail Removed)> wrote in message
>> news:A350DE60-6049-4AC3-954F-(E-Mail Removed)...
>> > Have created a small database in SQL Server 2008 Express and need to
>> > front-end it in Access. I can't create the DSN driver connection
>> > either
>> > from
>> > Access or thru Control Panel.
>> >
>> > Tried 3 different drivers. SQL Server Native Client 10 says: Could not
>> > open
>> > a connection to SQL Server [2].
>> >
>> > What am I missing?
>> >
>> >
>>
>>
>>
|
Similar Threads
