Sylvain,

>>Yes, it works but (as i did describe in problem 3), not in all cases. Besides this I simply think it is wrong to use the Uniqueness violation as an argument to never reuse PKs. It is a fact that this problem only exist when not using filtered primary indexes. Outside the xBase language this problem does NOT exist !!

>Considering that every DBMS system has it's own specifics, I don't see a problem. For example, while in SQLServer you can SELECT @@Identity, it doesn't work in VFP or Access. I don't know about Oracle. This doesn't make it wrong.

Again, I never said that the use of generated PKs is wrong, neither any other solution is wrong. However one solution seems to be more constructive and logical than others.

However I think that it is wrong to say that a VFP developer should be forced to use generated PKs, this is simply asking for problems. It depends on your situation.

>As for reusing PK, whenever I had a client who fell on that problem meant that the PK wasn't really unique after all.

huh ?? could you explain that ??

Walter,