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?
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only