VB to Access 2000

Hi, I'm trying to print a report in Access through Visual Basic and I can't get it to work with Access 2000. It works great with 97 but will not work with 2000. Am I missing something?

Thank you for any help!!!!!!

Amy

Do you have any of the Visual Basic service packs? I know either SP3 or SP4 (not sure about SP1 or SP2) has a fix for working with Access 2000. SP5 is out now at http://msdn.microsoft.com/vstudio/sp/vs6sp5/default.asp

I am using SP5 and still receive an Active X error when trying to execute the connection to the Access 2000 database. Are there any data components i'm missing or is there anything i need to do differently in my code?

Thank you so much for responding!!! Greatly Apreciated!

Amy

I'm going to assume you're doing everything programmatically--if you're not doing it programmatically then I have no idea.

You might want to check your references:
ADO: Microsoft ActiveX Data Objects 2.5 Library
DAO: Microsoft DAO 3.6 Object Library

If this doesn't fix it then I'm not too sure what could be wrong unless you've changed things within the database or in the code. When I moved form Access97 to Access2000 my problems were fixed when I started using a service pack.

Is there just one particular point that it craps out on? If so, what's that line?

Philip

I suggest you try EasyGrid OCX. It's very easy and powerful.
Maybe it will help you.
Download it from http://www.share2.com/easygrid/

You may need mdac 2.6. Try the following site:
http://www.microsoft.com/data/download.htm

Thank you for responding. I have all the data components updated and using service pack 5 and still getting that Active X error. Is the code different when talking to Access 2000 as opposed to 97? The program craps out when it hits the fist line to open the database and gives the the Active X error.

Thank you!!!!!

Amy

Post a snippet of your code and maybe someone can help!

How do you connect to ACCESS? Is it through referencing to ACCESS ACTIVEX library (Project->References)? If so, if I'm not mistaken, ACCESS97 and ACCESS2000 are using a different OLB files (file that you point to via Project->References).

ACCESS2000 OLB: C:\....\MSACC9.OLB (Microsoft Access 9.0 Object Library)
ACCESS97 OLB: C:\....\MSACC8.OLB (Microsoft Access 8.0 Object Library)

So if you developed your program on a machine that has Access97, then you have the reference to the old OLB and when you bring the same program to a machine that has Access2000, the OLB does not exist and that could be the cause.

Another option is to not do EARLY BINDING (via REFERENCE). Use the CreateObject() function to create the Access.Application object on the fly. This way, VB will open up the whatever version of Access installed on that PC.

-Cool Bizs

You Service Pack 4 or 5 not sure which on Micrsoft downloads