Crystal Reports 8.5 issue set TEXTSIZE 65534

Question

0.00/5 (No votes)

See more:

I'm having an issue with Crystal Reports and trying to see if anyone else has encountered similar issue with resolution.
I'm using Crystal Reports 8.5 on a XP machine that uses Stored Procedure to get data. Stored Procedure returns rows but the report doesn't return any rows.

Comparing my SQL Trace through Profiler while running Stored Procedure and the report, this message in SQL Profiler

set TEXTSIZE 65534

stands out.

While googling, I haven't been able to find a concrete solution so I'm hoping if anyone has encountered and resolved this issue. Thanks in advance.

Posted 18-Dec-14 7:49am

Bhis

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Bhis · Answer 1 · 2014-12-19T11:25:00

I was able to resolve this issue by making changes within Stored Procedure. I had to minimize the amount of memory I was using. I had 3 temporary tables created within the stored procedure that would get deleted towards the end of execution. To fix my issue, I had to drop these tables once it fulfilled its purpose. Somehow I suspect that my Report Engine was only allowing 1 temp table in memory during the process. Once I dropped the table right before I created another temp table, it seemed to work for me.