Using crystl32.ocx With Access 2003

[richardlafrance]

I use to register the crystl32.ocx then put the active X control (Crystal
Report Control) on the form name it Report1 and write the following code
assigned to a button:

Private Sub cmdPrint_Click()
With Report1
WindowShowRefreshBtn=True
ReportFileName = "C:\SomeReport.rpt"
Action=1
End With
End Sub

Now I get an error on .Action=1

Does anyone know if the code has changed for Access 2003 or is it that
Crystal XI doesn't work with Access 2003?

 

[Arvin Meyer [MVP]]

You might try checking the reference after putting the control on the form.
I am curious though why you would want to use Crystal Reports in Access,
when the Access report tool is orders of magnitude better. I even know VB
6.0 programmers who automate Access just to get the reporting tool.

 

[richardlafrance via AccessMonster.com]

You might try checking the reference after putting the control on the form.
I am curious though why you would want to use Crystal Reports in Access,
when the Access report tool is orders of magnitude better. I even know VB
6.0 programmers who automate Access just to get the reporting tool.

I use to register the crystl32.ocx then put the active X control (Crystal
Report Control) on the form name it Report1 and write the following code

[quoted text clipped - 12 lines]

Does anyone know if the code has changed for Access 2003 or is it that
Crystal XI doesn't work with Access 2003?

I find that Crystal is more flexible than the Access reporting tool. The
Access toll used to be a version of Crystal Licensed through Seagate without
all the bells and whistles. VB 6, VB.net, and VB 2005 all have versions of
Crystall Reports that come with them. They have changed the way that it is
used. it uses the Report Design Component (RDC).

The code in Access up to 2003 has been the same in VBA as it was in VB 6 but
it seems to have changed. Access doesn't seem to regcognize .Action = 1. If
you know what library that .Action can be found in this would be a big help.
It is not contained in the Microsoft Access 11.0 Object Library. At least it
isn't beeing recognized.

 

[Arvin Meyer [MVP]]

I find that Crystal is more flexible than the Access reporting tool. The
Access toll used to be a version of Crystal Licensed through Seagate
without
all the bells and whistles. VB 6, VB.net, and VB 2005 all have versions
of
Crystall Reports that come with them. They have changed the way that it
is
used. it uses the Report Design Component (RDC).

The code in Access up to 2003 has been the same in VBA as it was in VB 6
but
it seems to have changed. Access doesn't seem to regcognize .Action = 1.
If
you know what library that .Action can be found in this would be a big
help.
It is not contained in the Microsoft Access 11.0 Object Library. At least
it
isn't beeing recognized.

The Access reporting tool was developed by a team headed by Richard McAniff,
now a corporate VP at Microsoft. At no time did it ever use any part of
Crystal. In addition to Access, I also use VB 6.0 and have the enterprise
edition on my development machine. There is no copy of crystl32.ocx in my
VB 6.0 files. I did find a copy in an application that is installed on my
machine. Manually adding it to the system32 folder and trying to register it
also fails. It doesn't show up in Office XP as well as 2003.