I propose that you guys are doing something suspicious in these stored procedures. I use this technique all of the time in many different apps, and have never had that problem.

Would you be game for posting the procedure at fault?


>This same thing has happened to me, just a few days ago in fact. With a VFP6 app, I had a stored procedure to create primary keys, which resulted in the same error, even when I hadn't added any new records. I also had to move the procedure out of the DBC to get rid of the problem.
>
>
>>You're scaring me! I used to get that error often in VFP 5.0 when I tried to >use a stored procedure to assign PKs) and have yet to see it in 6.0 (knock on >wood). I'm afraid I never took the time to determine the absolute cause; I >moved the stored procedure out of the DBC. Are you using any types of >triggers or default values in your tables?