MSDE Connection Problem

[Mary_Chabot]

Good afternoon every one,


I have created a MSDE database using MS
Access 2000. When prompted for the SQL Server that
I wished to use, I selected (local). I named my

database
and gave it a username only "sa".

I then created my visual basic application
using the following command to connect to my database:

OpenConnection.Open "Driver={SQL Server};" & _
"Server=(local);" & _
"Database=mydatabase;" & _
"Uid=sa;" & _
"Pwd="

I can connect without any problems to my
database through my VB 6.0 application (I have Windows

2000).
Now that my development is done, I am trying to package

my
software for release.

I am using InstallMaker version 8.14. In
the database settings I have checked to install MSDE
and MDAC 2.6. However, once the installation is done
on another machine (either Windows XP professional or
Windows 98) my application is unable to connect to the
database and I get the following error message:

[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL

Server does not exist or access denied. - -2147467259

Would any one be able to tell me what is

missing
for my installation to be complete and successful? I
am thinking it is some thing I have not included in my
installation but I could be wrong. Any help would be
greatly appreciated.

Best Regards,
Mary

[nihar]

Could be due to a lot of reasons..

what is the network protocol which u have installed? i dont know which protocols does MSDE support by default.

I'd suggest using TCP/IP as the default protocol, remove all others if you are not supporting any other.

also try to establish connection to the server using a dsn or something on the client's machine. if you are able to connect then there is something wrong with the connection string.

try to use the sqloldedb1.0 driver to connect to the from the application. Sql books Online has this to say:

Attempting to connect to an instance of SQL Server version 7.0, running on the same computer as SQL Query Analyzer and SQL Server 2000, may fail under certain conditions. To avoid this problem, make sure that the shared memory protocol option within SQL Server Client Network Utility is disabled before trying to connect.

[mgiambrone]

Does the DCOM98 package have to be installed on the client machines?? This is just a thought.

I have had problems in the past when deploying an app to a client that didn't have MDAC installed.

[Mary_Chabot]

Good morning nihar,

Thank you for your reply. To answer your question, I use
the TCP/IP protocol only with my database.

As for connecting using the sqloldedb1.0 driver, I seem to not
have that installed on my computer. I will look into it and see
what comes out.

I have found the way to install the MSDE onto the user's
machine so that removes one problem. Now I only get a login
failed error so I must have some thing wrong with the way
I setup the DSN from my installation software.

Thank you for your information, I hope the sqloldedb 1.0 will
solve my problem.


Hello mgiambrone,

Indeed, the InstallMaker software allows you to include such installation as MDAC and others. I always include them because
like you, I have encountered problems in the past.

Best regards to the both of you,
Mary