 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
VB Forum / Database Access / May 2006Problem with MDAC 2.81 on Windows XP with SP2
Hi, I have a VB6 application with Access XP Database. I developed it on XP without SP2, and I had to install MDAC 2.8 to enable some ADO features (like search backwards in Recordsets). Now I'm trying to run this application on Windows XP with SP2 but many features in the ADO (the ones that requires MDAC 2.8) are not working. I tried to install MDAC 2.8, but it's seems that SP2 contains MDAC 2.81. My questions are why my app does not work with MDAC 2.81? Are there some known problems with this version? And is it possible to install MDAC 2.8 somehow? (Maybe install Windows XP without SP2, then install MDAC 2.8, and only then install SP2)? I would appreciate any help on the subject, Thank you very much, Tal. > Hi, > I have a VB6 application with Access XP Database. [quoted text clipped - 14 lines] > Thank you very much, > Tal. What do you mean by "does not work". What errors are you getting? What are you trying to do when the error occurs? As long as you have installed the correct MDAC package for your OS there shouldn't be any versioning issues. It is more likely a "permissions" problem. hth -ralph Hi, I don't get any errors, but strange behavior. For example: The following code rs.find "Item_Size Like '" & typed_Name & "%'", , , 1 works with MDAC 2.8 without SP2, but the same code with SP2 and MDAC 2.81 cause the rs to jump to EOF. I also have problems sorting the recordset. Thanks, Tal. > > Hi, > > I have a VB6 application with Access XP Database. [quoted text clipped - 24 lines] > hth > -ralph > Hi, > [quoted text clipped - 8 lines] > Thanks, > Tal. <snipped> Ah! That explains it. I thought you were getting a 429 or something. Yes there ARE subtle compatiblity issues with 2.8, 2.8 RTM (especially deadly), and 2.81. And with XP SP2 you are stuck with supporting 2.81 as you can not 'downgrade' to the others. (Not without potentially more grief than you have now. <g>) You have essentially two choices: 1) Downgrade (down 'bind') your original code to ADO 2.5/2.6/2.7 and lose some features, or 2) Install 2.81 on your development box. Also make sure you are using the same provider in both environments. Note: Whether you use Late or Early binding will not resolve this issue. The syntax will fail on one or the other no matter what. -ralph > > Hi, > > [quoted text clipped - 29 lines] > > -ralph Just for grins use the MDAC checker to make sure everyone is on the same page and you know exactly which version is being used where... http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53 -14332ef092c9&DisplayLang=en -ralph Thanks for the quick response. The problems still happen when I'm running the application from the VB IDE on Windows XP with SP2. Do I need to specifically install MDAC 2.81 on the development machine? Does the code should work when compiling it with SP2? I have another question: Does MDAC 2.81 is found on some SP of Windows 2000? Because if it's not, maybe I can change to Windows 2000 and use MDAC 2.8. Thanks, Tal. > Thanks for the quick response. > [quoted text clipped - 9 lines] > Thanks, > Tal. Let me be boorish for a minute and make sure we are on the same page... Each of the MDAC packages installs a suite of components that implements support for different ADO Interfaces. Think of them as the "Code Behind the Call". ADO is a specification for an interface. MDAC 2.8, MDAC 2.8 RTM, and MDAC 2.81 components all support "ADO 2.8". While it is common to refer to MDAC 2.81 as "ADO 2.81", this is a misnomer. It isn't a different version of the ADO interface, it stands for "MDAC 2.8 Service Pack 1", ie, they are different components to suport ADO 2.8. Your problem (if I understood it correctly) is that the components installed with MDAC 2.81 *implements* the same interface slightly differently than the behavior you are expecting when you used components supplied by MDAC 2.8. So ADO 2.8 isn't the issue, the issue is attempting to obtain the same behavior across different components. Unfortunately there is no way to do that in this case. You either have to use the same components, the same MDAC package, for both development and deployment, or you need to give up and work around the behavior differences, or you need to abandon ADO 2.8. MDAC 2.8 SP1 is only installed on Win2k if the user has installed it (after market). If you are bound and determine to use these components then include it with your program. http://www.microsoft.com/downloads/details.aspx?familyid=78CAC895-EFC2-4F8E-A9E0 -3A1AFBD5922E&displaylang=en HTH -ralph Hi, I think I understand you, but I want explain you again my configuration: In machine A the app is working. This machine has Windows XP, no SP2, and MDAC 2.7. In the VB IDE, I've selected ADO 2.7 (in the project>references). In machine B, the app is not working. This machine has Windows XP, with SP2. The app is not working when I select ADO 2.7, and also not working when I select ADO 2.8. If I understood what you explained me, there is no way that the application will work on machine b without code changing. Am I right? Thanks, Tal. > Hi, > [quoted text clipped - 13 lines] > Thanks, > Tal. If the "is not working" still refers to a difference in behavior with the .Find method then yes you will have to lose the feature, or install MDAC 2.8 SP1 on your development box. But then I am still concerned that I don't really know what "is not working" means. -ralph |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.