Error " Invalid Parameter Field Name"

[cpaige]

Hey,
We have an application here that will read a directory tree and allow us to view reports that are present in the structure. This program was developed with VB and the CRviewer. The problem I am having is that when I run a report without parameters, the error "Invalid Parameter Field Name" pops up.

I was having the exact same problem with another report and I went on to the Crystal Site and it gave me a solution. The solution was to remove any extra P2SORA7.DLL files that might be present on my computer. I have done that and it has solved that problem for that report. Now, this report is giving me the same message and the Crystal Site doesn't have any more solutions.

Does anyone have any ideas?

Thanks!


Clayton T. Paige
claytonpaige@yahoo.ca

Programmer Extraordinaire

========================================================

"Who is General Failure? and Why is he reading my disk drive?"

 

[synapsevampire]

Or perhaps the SP isn't properly constructed?

A reserved word *might* cause problems, or the wrong type of connectivity.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[cpaige]

Please define SP?
Is *might* a reserved word for SQL or Crystal. I'm only using Crystal 6 and I don't think it supports that reserved word. At least not to my Knowledge.
Clayton T. Paige
claytonpaige@yahoo.ca

Programmer Extraordinaire

========================================================

"Who is General Failure? and Why is he reading my disk drive?"

 

[synapsevampire]

Sorry, I misread the original post. I thought that you had parameters and assumed SP's (Stored Procedures).

You have reports without parameters that are returning the error, that's odd indeed...

I'd save the report under a different name, then dissect it by removing fields and then tables and see if the error persists. Perhaps there is a naming violation involved, and dissecting it might be the fastest way to uncover it.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[cpaige]

Eureka

I found the problem! When I followed Crystals support instructions it said at one point that if you there are more then one of the P2SORA7.DLL files on the computer then to leave the one in the c:\Windows directory.

This help must have been written pre-windows 2000, because there is no Windows Directory in Windows 2000 and the DLLs are stored in separate directories. When I did a search the 2 files were found in the C:\winnt\CRYSTAL and
C:\winnt\system32. Well, both files seemed to meet their criteria for keeping. The (WRONG) way I decided which file to rename was by age of file. I renamed the older file, which was WRONG.

I went back and renamed the newer one and my problems have been solved. The reports run fine now. I guess that upgrade was really a downgrade. I think the best rule is to keep the file in the system directory.

Thanks for you help
:^)
Clayton T. Paige
claytonpaige@yahoo.ca

Programmer Extraordinaire

========================================================

"Who is General Failure? and Why is he reading my disk drive?"