drosenkranz
Programmer
Hello,
I'm using VB 5 (DAO) and Access '97 with Crystal Reports 7 on Win '9x machines. We are now replacing older machines here with Win XP Pro. We also have a new server running Win 2000.
Some of the reports (that have been in use for years) will not run from the OCX embedded in the VB forms yet they still execute correctly from the Crystal Report Designer. I think the conflict is that Win '9X and Access '97 PC's use the DAO350.dll while Win 2000/XP and Access 2002 PC's employ the DAO360.dll. I think the P2bdao.dll, P2irdao.dll and the P2ctdao.dll's may also be relevant.
Can anyone point me in the right direction for a work-around?
Thank You,
Dave The 2nd mouse gets the cheese.
I'm using VB 5 (DAO) and Access '97 with Crystal Reports 7 on Win '9x machines. We are now replacing older machines here with Win XP Pro. We also have a new server running Win 2000.
Some of the reports (that have been in use for years) will not run from the OCX embedded in the VB forms yet they still execute correctly from the Crystal Report Designer. I think the conflict is that Win '9X and Access '97 PC's use the DAO350.dll while Win 2000/XP and Access 2002 PC's employ the DAO360.dll. I think the P2bdao.dll, P2irdao.dll and the P2ctdao.dll's may also be relevant.
Can anyone point me in the right direction for a work-around?
Thank You,
Dave The 2nd mouse gets the cheese.