Do not expect a miracle from me. I am still in the dark on many issues,
however, Sql Servers do work on my machines and I did have trouble
connecting to them even locally. Not anymore.
Let me draw a scheme as to how it probably works in your LAN. Those details
are important.
You have an XP machine where Sql Server resides, aren't you? This is the
server with your databases.
Then you have an application "app1" which is a client, am I correct? You
used to have it on another XP? Before you could easily connect to your
server. Am I correct?
Now you moved your client (app1) to a Vista machine and left the server on
XP.
You get this network exception. All your data traffic is confined to LAN? Am
I correct? There is no connection with the www server or anything, I
presume. I also assume that you do not create any sockets to connect to your
Sql Server. I mean, your app does not do it. It is actually is a
possibility.
Now, if this design is what realistically you have set up in your LAN, I
will need a confirmation. However, I will rush ahead and make a rash
judgment that my hunch is that you've got your network exploration options
perhaps messed up or not set up at all.
Please excuse me if my questions appear to be too simple and you have
already verified all of this. Have you tried to connect to the other (XP)
machine manually to just check if the directory is accessible thru
Start>>Network, etc? Do you see the other computer from your Vista? Are you
able to see some parts of your vista machine directories from XP? Can you
actually poke thru files?
Do not run your app1 until you did some simple things manually.
So, if you could provide some of this information that may be helpful and
please, be specific.
If you come back saying that you'd got all this checked out last year, we
will have to elevate it to a higher level.
If you can see Sql Server DBs folders from your Vista and the things still
do not work, do not despair because it is what supposed to happen. If you
are an administrator you must get ownership of these database files .mdf
PLUS the .log file for each DB individually. It is possible that the
ownership may be an overkill but you must set yourselves up as a user with
fill access. I mean that your app1 must become that user. It may be in
indirect way. You may actually include this app1 as a member of the
Administrators Groups in Local Users and Groups GUI (it is all in Vista) but
you will probably have to extend the Vista reach into your XP with the same
set of rules that Vista is using to protect your Sql Databases if thy are
located in XP.
Incidentally, if you have your Sql Server alone in XP, why don't you use
WinServ2003 or even 2008?
Ok. some of it may be a bit incoherent since as I've said, I am not a great
expert,I am just learning myself.
Now, with MDAC, I cannot honestly answer this question at this moment. There
is a tiny an embarrassing problem here. I checked this machine and it is not
listed among my programs. I clearly remember that I downloaded and installed
it. Answering your question how you could install it. It is very simple. I
am an MSDN Pro subscriber and I do have access to all their downloads but it
is my recollection that it is accessible to everyone. You should check MS
downloads.
Now, why do I not see it on my Vista? For a very stupid reason my Vista
crashed on Dec 24 (a Christmas give I made to myself). After a brief
analysis and some fortuitous observations I realized that it was my own
fault, I rebuilt the system again and apparently that download was left in
there. I since erased Windows.old folder.
I will download it again, thanks for the reminder. It may not be so crucial
for your, in fact. It may be more for OleDb people. I do this stuff as well.
It seems I do have an exception coming up without MDAC present, so maybe it
will help.
There is also a chance that MDAC is also installed on my other machine but I
have no access to it now. I will check.