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.
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.