>This is quite interesting to many people, I'm sure. Just recently we ran across the same issue in an application written in VFP 5.0. I'm curios, does anyone know if this bug has been resolved in VFP 8.0 - at least to the point that an error displays notifying the user that the record could not be inserted?
Yes, though I haven't tested it much yet. There's a new command in vfp8, can be used at runtime,
SET TABLEVALIDATE TO [nlevel]
which should help catch these things.
The Anonymous Bureaucrat,
and frankly, quite content not to be
a member of either major US political party.
