mjimeno
asked on
I get error 3051 when trying to connect VB with Access DB in a remote PC under W2k
I have a VB application which tries to connect to a MS Access 2000 database located in another PC within the network. When I try to do it with the remote PC under Windows 98, it connects correctly. The problem is that I can't connect to the DB when the remote PC is under Windows 2000 Professional. It shows me this error: << "Runtime Error 3051: The Microsoft Jet database cannot open the file '\\remotePC\SharedFolder\d
Thanx a lot for any help and for reading this long question.
Thanx a lot for any help and for reading this long question.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It will be better for me, if I find a way to solve that problem, which does not include a odbc connection. I am using a DAO connection, with OpenDatabase(...), etc and it is a large code that will be quite difficult to change from DAO to ODBC, I mean all the connections and related stuff. And about the account, I have partially solve the problem by login both pc's to the same domain, but that was a recreation of the problem in the LAN of my company, and I need to solve it in my boss's company (other place), where I have not 100% access. I know that both pc's are W2K, and both are in the same workgroup, but I don't have much information about accounts and users.
ASKER
I will appreciate if KeyPakt could give me a clue about how to create that account to connect to the db. Maybe I could try it to see what happens. That account is for the file or for the SO? thanx!
ASKER
KeyPart and someone from my company gave me the idea to solve the problem: As easy as (it was not so easy for me) enable the user Guest, which is disabled by default in Windows 2000. In the PC under W2K where the DB is located, I went through Control Panel --> Administrative Tools --> Computer Managment, under System Tools I found Local Users and Groups. There I saw the user Guest with an X (disabled). Then I enabled it again and then anybody could run the application and connect it to the DB located there. That's all. The only doubt I have is that I don't know how secure will be for the PC under W2K if I enable the user Guest. So, thanx to KeyPart, you were the closest. Bye
Then it will help you os looking after the connection from one computer to another.
U give all the username and password criteria in odbc.
I hope this will help you.