Link to home
Start Free TrialLog in
Avatar of grant-ellsworth
grant-ellsworth

asked on

crystal reports mssql HY010 function sequence error

I have a crystal report which was working the last time we ran it 2 months ago.  when I run it now, it generates error message HY010 Function Sequence error.  The report is accessing a MSSQL 2005 database via ODBC
Avatar of Mike McCracken
Mike McCracken

That is not a Crystal error but an MS SQL error.

What has changed since you last ran the report?

mlmcc
Avatar of grant-ellsworth

ASKER

>> mlmcc:That is not a Crystal error but an MS SQL error.  What has changed since you last ran the report?  mlmcc

Interesting ... Major change in database: content updated and many columns added / others deleted in one table - altered table not referenced in the reports.
One thing to try
Open the report in the designer
Click DATABASE --> VERIFY DATABASE
Follow the prompts
SAVE THE REPORT
Try running the report

mlmcc
>> run Verify Database

Already tried that - still got the error message.
Can you build a new report using the same ODBC connection?
If not, can create a NEW ODBC connection to the databse and build a report?

mlmcc
already tried that - simple report worked.
Clarification = already tried building simple report using tha odbc db fields.  It worked;
Look at this discussion

http://forums.sdn.sap.com/thread.jspa?threadID=1624596

Bottomm line of the discussion
The error was occuring because of the System attribute assinged to the C:\Temp folder on my server.

Once I ran this command... ATTRIB -S c:\temp

mlmcc
ASKER CERTIFIED SOLUTION
Avatar of grant-ellsworth
grant-ellsworth

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've requested that this question be deleted for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
I object since I now know that I posted sequence that solved problem.  This might be useful to somebody else.  Take it off of auto close and i'll close the case indicating the solution.
After reboot, the solutiion "stuck" ... there my experienc showed that the problem could be solved - but I don't see quitee why the ijnitial reboot was necessary.  I submit this solution instead of proceeding wiith deletion beecause the problem and solution might be useful to somebody else.