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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ADO 2.5 vs ADO 2.1

Status
Not open for further replies.

Chopstik

Technical User
Oct 24, 2001
2,180
US
I have created a simple .dll file for use with my .asp pages. When I moved the file out to the web server, it does not work and I spent a great deal of time trying to figure out why (particularly since the .dll file worked on my local machine when using within another VB app). I have now come across the msado15.dll file that I referenced within my own component.

The msado15.dll file on my system appears to be much newer than the one on the web server. Indeed, mine is for ADO 2.5 while the one on the web server appears to be for ADO 2.1. My question is whether this would cause a problem since I developed using the newer version but the server is running the older version? Would it cause my component not to work on the web server? Does this make sense? Thanks for any help or thoughts on this matter.
 
that depends on what you're using of the mdac library. if you're just using connection objects, recordset objects, etc it might still be ok, however if you're using things like stream objects it might have a cow. codestorm
Fire bad. Tree pretty. - Buffy
select * from population where talent > 'average'
<insert witticism here>
 
Well, I upgraded to MDAC 2.5 on the web server, and it appears to have solved the problem. However, that said, I was also only using the recordset option within my component, so can't imagine why there would have been an issue. Of course, I was also referencing the comsvcs.dll file in my component and that presumably would have also been upgraded when I did the MDAC upgrade, so not sure if the issue might have been there as well/instead. (I was using the object context which is why was referencing the comsvcs.dll file in my component.) Do you think this may have been the issue instead? Give me liberty, or give me pizza...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top