Isn't there a guru that can help me! -- I urgently require major assistant! Please HELP!

[marci_sarwan]

Hello Gurus of the world,

I desperately need your help and I am running out of option. I created a database dialog based application using VC++ and I'm using ADO along with MS ADO DataGrid and
MS ADO Data Control to connect to the database (an Access database that reside on the LAN). The program works perfectly and I created a setup file so that I can
distribute it amount my co-workers. The problem I'm running into is that it works on some machine and on other it doesn't work. The program runs on EVERY machines
and the user interface appears but on some machine it doesn't connect to the database when I try to do a search using the program. I have determined all the dlls that my
program required using the Dependency tool from VC++ Studio and I installed it along with dcom98.exe and mdac_typ.exe right afterward and it still doesn't connect to the
database. I'm running out of options and I read all of Microsoft support webpage and I still don't know how to resolve my problem. Can someone kind enough tell me how
to make this work -- I've been working on this for a while and still I'm not able to make it work on some machine. I appreciate all helps and welcome all suggestion. Thank
you in advance!


Marci Sarwan (marci_sarwan@yahoo.com)

[Johnny101]

my first suggestion would be to make sure that any DSNs that are needed are there. Since all the necessary files are there (MDAC etc) it's not a dll problem, but it seems to me that that machine can't see the database - which implies, either there is a network restriction from that machine to the db server or the DSN entry is corrupt or missing. check out the ODBC section of the control panel on a machine that it works on and compare to the machine that doesn't work.

hope this helps,

John

John Pirkey
MCSD
http://www.ShallowWaterSystems.com
http://www.stlvbug.org

[marci_sarwan]

Hello John,

thanks for replying! I compared teh ODBC section of the control panel on a machine that works with a machine that doesn't work and it looks identical. This is really strange because I can manually open the database from the machine that can access it through my program. Another, interesting thing is when I rename the database and try connecting it with my machine (good machine that connects properly) the system gives me an error complaining that it can't locate the database however, when I try connecting to the database after it is renamed using my program on a machine that the program doesn't seem to connect there is no error message -- absolutely nothing. Some people have suggested that I'm missing the ADO control but then if I'm missing it how come it works on some machines? I have tried almost everything that is possible and am running out of options. I hope you can help me! I also posted this question in the Visual C++ Programming forum and there are at least 25 replys to my questions so you might want to look at it. Thanks a lot!



Marci Sarwan (marci_sarwan@yahoo.com)

[marci_sarwan]

Hello John,

I created a very simple dialog base program that consist of a MS DataGrid Control Version 6.0 (OLEDB) and a MS Data Control Version 6.0 (OLEDB). There's no code at all and all I did was set the connection string property of the Data Control to point directly to the database that sits on the LAN. When the program is executed an interface appears with the grid populated with records from the database. Again, the program works on some machine and doesn't on other. So, what do you think is wrong? Thanks!


Marci Sarwan (marci_sarwan@yahoo.com)

[Johnny101]

I'm still convinced that there is a physical network limitation preventing access to the database from the problem machine. Is this Access database located on the same machine or on a network share? does the real app use SQL Server or Access? if it's SQL Server, try opening a DOS prompt and pinging the server. if you can't ping the server, this is the problem, contact the network administrator and talk it over with him/her. if you can ping the server, then i'm not sure what could be hapening. one thing that may be applicable here - when the setup is ran for yuor app, i assume it's ran by the current user - the MDAC MUST be ran by someone with Admin rights on the LOCAL box. if the typical user is not a member of the Admin group on the local box, then you have to find some way of running the install as the Admin, or arrange for the users to be added to the Admin group long enough to run the install. this is a long shot, but it could be a possible trouble area.

if the main database is an Access database on the local box, make sure it's not marked as read only or password protected. if it password protected, make sure that all necessary security info is passed correctly.

i hope one of these is the problem, because i'm out of suggestions (sorry). let me know how it goes.

good luck,

John

John Pirkey
MCSD
http://www.ShallowWaterSystems.com
http://www.stlvbug.org

[marci_sarwan]

Hello John,

no the Access database is located on a shared network. Everyone, is connected using Novel. The app uses Access. With regards to making sure it's not marked as read only or password protected and all neccessary security info is passed correctly -- how do you do that?

Marci Sarwan (marci_sarwan@yahoo.com)

[Johnny101]

If the database is marked as read only, it will have the Read Only flag set, you can check this by right-clicking the file in Windows Explorer and selecting Properties. there's a check box at the bottom of the dialog box that pops up indicating that.

as for the security info, since it's a single database and other machines use it, i would guess that there aren't any security parameters. granted the other machines are using the same source code (exe) as the problem box and they can connect - this pretty much rules out the security possibility.

one thing to ensure is the network share is mapped to the same drive (if the path to the access database is hardcoded in the source code) and make sure that it is accessible from the problem machine and that the normal use has access rights to that share.

other than that, i can't think of anyting else that could cause these problems. as a last resort, you might consider loading VB onto the problem machine and stepping through the code to see what exactly is happening and where it failing.

good luck,

John

John Pirkey
MCSD
http://www.ShallowWaterSystems.com
http://www.stlvbug.org

[marci_sarwan]

Hello John,

I'm using the Universial Naming Convention to access the server so it doesn't really matter what drive letter the client maps it to. If I install Visual Studio on the machine that doesn't connect to the database I wouldn't have to step through my program because I'm sure it will connect then. This problem is killing me..... Thanks!

Marci Sarwan (marci_sarwan@yahoo.com)

[chakree d rani]

Why don't you think in the perspective of versions?

Rani

[marci_sarwan]

Hello Rani,

I'm not sure what you mean -- can you elaborate on this? Thanks!


Marci Sarwan (marci_sarwan@yahoo.com)