PDA

View Full Version : Crystal Error with VDF10 or 11 and CR9



Joe Coley
6-Jul-2005, 12:44 PM
When running a report compiled from VDF, it works. When running the same
program from a shortcut, I get an error. I have narrowed the error down to
occurring in the CrystalReport.pkg in the following line:

Procedure StartPrintJob // Integer iWaitUntilDone
Integer iPrintJob iResult iObject
Get PrintJob To iPrintJob
// note that the statuspanel logic is private (and unused). This could
// change in the future
// Check if there is a status object...
If (StatusPanel_Id(self)) Begin
Move (StatusPanel_Id(self)) To iObject
// in case this pkg is used inside of a set of packages that does not
support
// the label property, we will exclude this from the code. Even if supported
this
// only works if the container object supports the label property.
#IFDEF SET_LABEL
#IFDEF GET_LABEL
Set Label Of iObject To (Label(self))
#ENDIF
#ENDIF
Send Popup To iObject
End // If (StatusPanel_Id(self)) Begin
Move (PEStartPrintJob(iPrintJob,True)) To iResult <<----- ERROR HERE
Send HandlePossibleError
// Stop displaying status info...
If iObject Send Deactivate To (StatusPanel_Id(self))
End_Procedure // StartPrintJob

This happens on several different machines. Any ideas on what to look for? I
only have CR9 installed on this machine. Again, what is odd, is that it
works straight from a compile and not from a shortcut.

Joe Coley (with help from David Martinko).

Joe Coley
6-Jul-2005, 07:56 PM
I get 2 different errors using the shortcut depending upon whether the
machine is WIN2000 or WIN SERVER2003. Screenshots of the errors are
attached. Another strange thing about this problem is that I'm now testing
with 2 different reports -- one works under all circumstances, one fails as
described. This is REALLY strange! The .rv's for the 2 reports are pretty
much the same.


"Joe Coley" <sjoec@charter.net> wrote in message
news:FXVPQJlgFHA.1112@dacmail.dataaccess.com...
> When running a report compiled from VDF, it works. When running the same
> program from a shortcut, I get an error. I have narrowed the error down to
> occurring in the CrystalReport.pkg in the following line:
>
<clip>
>
> This happens on several different machines. Any ideas on what to look for?
I
> only have CR9 installed on this machine. Again, what is odd, is that it
> works straight from a compile and not from a shortcut.
>
> Joe Coley (with help from David Martinko).
>
>

Peter A Donovan
7-Jul-2005, 05:26 AM
Hi Joe,
Are you using David Martinko's code to auto-locate the data file without
setting the report to "same folder as report"? I just have some issues
come up where Norton Antivirus interferes with this code.
Regards,
Peter

Joe Coley
7-Jul-2005, 06:22 AM
Actually Peter, what seems to be the cause is that I'm using a mapped
drive -- in this case "T:". If I create the shortcut to the mapped drive, I
will get these errors (although a report accessing only one data file seems
to work!).

However, early testing (or should I say late last night :-) indicates that
if I instead use UNC address in my shortcut (\\mendon2003\vdf11\myapp.exe)
then all appears to work properly. (On the server using a shortcut directly
to the app also works properly.) This appears to be repeatable as I have
the situation on my development network, and the same experience at my
customer site.

I am using David's code (with some of the reports that were failing, but not
all), but, when David and I were checking this out yesterday, we stepped
through the code with the debugger and error occurred in the code as shown
on the first message of this thread -- not within the code he had added. As
a test I eliminated the code and just used vanilla CrystalReport with the
same error.

Relative to problem with Norton AV, on my customer site they are using
McAfee, while on my development site I'm using Norton. Go figure! :-)

Todd Forsberg
30-Jun-2011, 03:16 PM
Thank you Joe!

I was getting this same error today. I removed the mapped drive and "Poof!" the error went away. Six years later and the info is still helping people. Thanks!