Vb6 Adodc

I have a VB6 application .exe file located on a network server. There are 3 users that access this application via a shortcut located on their individual computer Desktops. When I sign into the application from 2 of the computers all works fine, but on one specific computer a datagrid within the application will not populate using an ADODC connection. I thought that the .exe bundles all the References, Components, etc that the application requires. Why would 1 of 3 computers not work properly? Is there a dll file that I must register on that specific computer? Any ideas on what I should look for? Thanks for your time. Regards

 

make sure that pc has the latest MDAC installed

 

Will give that a try.
Appreciate your assistance
Regards....

 

you may also want to take a look at this

Matt

 

Matt,

I'll see if that helps also.
Great - I apprciate the help
Thanks again

 

As noted in previous thread "VB6 ADODC" I have a VB6 application that
is being used on a network. The network is using OS Windows2000 Professional, which I have been told ships out with MDAC 2.5.
My computer has MDAC 2.8RTM. I have recompiled the VB6 application
and placed the .exe out on the Network for user to access via shortcut.
The user computer has had MSADODC.ocx downloaded, and MDAC 2.8 downloaded. This did not fix the issue. The datagrid will still not populate but does work fine on some other PCs within the network.

Does anyone have any other ideas as to what to look for?
Appreciate your time and assistance.
Regards
Mike

 

Mike,
have you checked the event viewer to see if there some other reason why the data is not populated? perhaps the ADODC control is working fine but the access (permissions ??) are preventing the user from accessing thed data.

 

kodo,
I had, so to test that we signed into the application as the 'Administrator'
on each computer, resulting in the same issue. Currently our 'fix' is to
properly 'package' the project, then install the packaged application
directly onto each computer. This is not as flexible to maintain as simply
placing the .exe out on the Network, but I guess my "cutting corners" created my problem. I appreciate your time and suggestions.
Thanks