20561: Error in File : invalid value type

[DeafBug]

A client of ours is having problems with printing statements and it has been two weeks. (The only client of out many.) They are getting upset as the statements is a monthly thing. I have no idea what is causing the problem and I have no idea where to look. I have google'd it and nothing came up. I even looked at the Crystal Decisions KB and nothing came up either. The Develepor Help file is no good either.

The error message is "20561: Error in file C:\Program Files\...\Statement.rpt: Invalid value type."

What is causing this error? I have a feeling that a DLL file is corrupted, missing, or damaged. I thought it could be the data but it doesn't appear to be. Any ideas where to get more information on that 20561 error?

Thanks.

 

[synapsevampire]

Please post something about your environment, Crystal version, database, OS, how reports are deployed (VB?), when this error occurs, etc

Does it work for a while, and then stop working?

Perhaps you are opening multiple versions of the report through an application, but not closing them, and you're hitting the max number of open reports?

-k

 

[DeafBug]

It is VB6 with CR7 using the automation control using MS SQL Server 2000. The client is running XP but other clients run on either XP or 2000. Everything to the latest service pack or patches. (Part of the agreement with us.)

It worked for sometime with that client then all of a sudden it stopped. We are in the processing of getting their database backup so we can run it locally and see if it is data related. We strongly feel that it is not but it will help rule it out. But part of our hutch is that the client may have done something and haven't told us. We have looked at their Event Log and found nothing out of the ordinary except that they may have problems with the printer. But... we have over 60 report files. It is just that one report file that doesn't work. The printer they are using is a Lexmark laser. The last changed made to that report file (according to VSS) was almost a year ago so it shouldn't be the problem.

Most of the fields in the report are strings, a couple datefields, and 3 currency fields and a few number fields otherwise nothing we can think of that will stop it. We even did manage to get only two records returned from the SQL and it still caused that error.

 

[DeafBug]

Solved the problem.

The client had another program installed and it overwritten two of the CR7 files with CR8 files. The CRYSTL32.OCX and CRPE32.DLL were in version 8. So I unregister them and renamed the files. Copied version 7 in the same folder and register them. Problem solved.

I don't know what application on the clients computer uses version 8 files. But they told us that they haven't installed or upgraded anything the in past few months. So if they are not telling us then so be it. We decided to leave it alone. So when the client runs whatever application that relies on version 8 files, it will break. Their fault not ours as they told us that they did nothing. (yeah, yeah, right, pants on fire.)

I thought CR made the files backward compatibility with same names like MS does. I guess not.