Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I just wanted to say THANKS for the forum. The knowledge I gain from your site is invaluable..."

Geography

Where in the world do Tek-Tips members come from?

(FOC1406) SQL OPEN CURSOR ERROR solved by selecting records

ekl0908 (Programmer)
9 Apr 10 17:53
In reference to the question in thread347-871635: Focus Error

I had a similar problem this week. I was running a procedure and I got the following error:

(FOC1406) SQL OPEN CURSOR ERROR.

The error occurred intermittently, not every time the procedure was run. It gave me the name of a table used in the procedure.

I thought it might be an issue of the number of records being read. So I changed the procedure to omit most of the records and use only the ones we need, and it then ran successfully. I made sure to select by a key field.

Then the administrator of our SQL server found that there were a few records missing from the table. There is a JOIN statement in the procedure, and when it reads all the records, it is trying to join one table to another table which does not have every matching number. When it uses only the records we need, it does not use those numbers which are missing in the second table. So that might be the cause of the error.

I don't know if it is a file size issue, or an issue of a JOIN statement which is not finding a matching record. But I managed to solve the problem by using an IF statement after the TABLE FILE statement, to omit the records we don't need to include.

I hope this is helpful to anyone who receives this particular error message and wants to track down the possible causes of it.    

 bigsmile  

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close