>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?

Hi Daniel:

The bad news it that the error happens, the good news is that it only happens in the VFP development environment, not in the final executable. Whew?

"Are you using any types of triggers or default values in your tables?" Oh, yes. All kinds.

Our first cut, since stored procedures are so difficult to track and debug, is going to be to most of the sp code into a code library. That should make it easier to see exactly what sp is hanging up, if any. I hope some code error is present. Coding can be fixed, VFP bugs are a little harder.

If you think of any thing else you might have done to "fix" the problem, please let me know.

regards,