Dear Fificat,
The error indicates that at some point in your Stored Procedure it is trying to use a character (varchar) and cannot convert it to an number (integer).
You state it runs on some machines and not on others.... and so on.
However, you did not state your testing methodology.
Now, why could it happen ... it could be a number of reasons:
Most likely: You use some database field that you thought only contained numbers, but in reality since it is really a varchar field it can contain text data and whenever your sp hits that field, it abends with the above error.
I wouldn't presume to think it is the number of columns. While I have never approached that number in an sp I certainly have in reports based on views and Crystal shouldn't care.
To me, a more valid test would be to test the sp in SQL Query Analyzer using the same parameters you are using for the report and check what happens.
Also, when I don't get the results I expect ... I look to the data itself. I would verify all of the columns I am using in my sp are of the datatype I think they are and would get it running without errors in Query Analyer before using it in Crystal Reports.
However, all of the above is guessing because I do not know what is in your sp. If you are not a SQL DBA maybe you
More info on what you are doing might be helpful.
regards,
ro
Rosemary Lieberman
rosemary-at-microflo.com,
Microflo provides expert consulting on MagicTSD and Crystal Reports.
You will get answers more quickly if you read this before posting: faq149-3762