Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VB6, MTS, SQL 2000

Status
Not open for further replies.

GeriR

Programmer
Jan 3, 2002
9
US
Hi:
Hope you can help. I have a vb app that uses mdac 2.5 (running on Win95) with an MTS server (running NT) that talks to SQL2000 (running on Win2K server).
I have this 3-tier configuration running on many different workstations (NT, 98, 2K & 95), with SQL7 or win2K, but always with MTS running 2.5 on NT server. No problem. In any event, in the above configuration (95,NT,2K) the app is throwing Error 7005 rowset not available if you open the app and go first to the form that uses datagrid with ADODC ocx.
If after opening the app, you first go to a form that retrieves data thru an ADO connection it does itself, and then go to the form with datagrid everything is fine.
Any ideas? (I have installed DCOM95 on the workstation, comcheck checks out -- I'm stumped)
Thanks in advance for any help
 

You may need to copy (and regsvr32) the file "MSBIND.DLL" on the machine(s) where your application is running...

The PDW in VB 6.0 shows MSBIND.DLL in the Out-of-Date Dependencies when packaging with an ADODC. It was supposedly fixed in SP3, but you don't specify what you used to deploy the app...


Mark

"You guys pair up in groups of three, then line up in a circle."
- Bill Peterson, a Florida State football coach
 
Hi Mark:
Been there - done that :eek:) - unfortunately NO Luck! (forgot to mention that I already tried that - sorry) BTW, I'm using Package & Deploy Wiz to build the intallation.
Any other ideas? Really appreciate it.
Thanks
Geri
 
Hey Mark:
Just a thought, maybe I just put the same stupid MSBIND version there. Do you happen to know what version I should be looking for?
Thanks again
Geri
 
Me again = I just double checked. No luck. I have the SP3 versions of both MSBind.dll & MSAdodc.ocx as described in Microsoft's article Q230733 (unless that's not the latest?)
 
My advice is to probably upgrade the MDAC on all the machines. I've known MDAC 2.5 to have it's share of problems, and I've since moved to the newest (2.8?) and had no problems with MTS (and now COM+ under 2k Server). I


Mark

"You guys pair up in groups of three, then line up in a circle."
- Bill Peterson, a Florida State football coach
 
I totally agree - but u know the powers that be. Unfortunately I don't have that luxury. It's always next time we'll upgrade but u know if it works they won't fix it!
And if it doesn't work, they expect you to make it work (of course without fixing it)
Oh well - guess I'm in a fix ? in a bind? (no pun intended). I know it's got to be some stupid config issue that's different on either this workstation or more likely the MTS Server.
Thanks for your thoughts.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top