Crystal Reports 7.0 RDC in Visual Basic 6.0

[charleyhorse37]

Can anyone help? I installed Crystal Reports 7 and the updated dll files from the SCR site. Using the RDC from within Visual Basic 6 I selected Standard Report, Project, then DAO, after that I selected a microsoft access 2000 database, but when I attempt to pick from a list of database objects, there are none displayed.

I know that the drivers are not corrupted and are the most current.

I'm stuck. Can anyone tell me what I've missed?

 

[kenhamady]

There is a FAQ on Access 2000 in the general forum:

faq149-552 Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[charleyhorse37]

Thank you for your rapid response to the question I posted to TEC-TIPS.

Unfortunately, your tip was something I had already done.

I am attempting to develop a database solution for my business (attorney).

I use MS Access 2000 as my database and have written the front end using Visual Basic 6. This program works fine for me and I can manage my clients and case load well.

However, I want to generate paper reports etc, and to facilitate this I bought Crystal Reports 7.

I downloaded the MR1 drivers for MS Access 2000 and uploaded as directed.

I have no difficulty creating a report through Crystal Reprts 7 Professional). My problem lies within Visual Basic when trying to create a report using the RDC from within Visual Basic 6.

As I mentioned in my previous query, when I access the RDC through Visual Basic, select DAO, and further select the name of the MS Access 2000 database, the RDC does not display any database objects.

This problem with Visual Basic acts like Crystal Reports 7 did prior to installing the new drivers, however, after the new drivers have been installed Crystal Reports works fine.

I want the Crystal Reports RDC that I access through Visual Basic to work.

Any thoughts?

 

[kenhamady]

It sounds like the old project is either using the old driver, or old components/references.

As a test, I would try creating a new simple VB project from scratch. Adding fresh components/references and making sure that the connection is using the correct drivers.

You don't have duplicate, possibly conflicting copies of the drivers on this PC do you? Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[charleyhorse37]

Ken,

Thanks again for the reply. I decided to unload Crystal Reports 7 and Visual Basic 6 from my computer and start again. I also erased all instances of the old and new drivers from my computer. After reloading VB6 and CR7 and updating the various releases and adding the new drivers, I did as you suggested and started a new VB6 Project, etc.

Same problem. I'm wondering if this is an intrinsic problem between MS Access, CR7 RDC and VB6 that has not been identified before?

I have no problem doing what I want to do with any Access 97 Database and the CR7 RDC via VB6. This problem only presents itself with Access 2000.

I also have no difficulty making a report in CR7 and accessing it through the Crystal Reports Control (CRYSTL32.OCX).

I'm sure I have overlooked something but I'll be darned if I can figure out what.

 

[kenhamady]

That is strange. It seems like you are still using the old drivers, but I can't see how. I have never tested that combination, but I would guess others here have and might be able to comment. You might even want to ask a question that is headed:

Anyone using RDCv7 & Access 2000?

Can you create the report via CR but launch it via RDC?

Can you import the report into the RDC to create the DSR file?

Good luck. Ken Hamady, On-site/Phone Crystal Reports Training/Consulting
Quick Reference Guide to using Crystal in VB

http://www.kenhamady.com/

 

[charleyhorse37]

Ken,

The problem is solved. I called Crystal's tech support and presented them with the problem. After trial and error it came down to a bad maintenance release cd. After I received a new MR1 and installed it, the problem was corrected.