Long estblished Database - 35000 parent records and 85000 child records. Edited a child record (one of 20 child records of that particular parent record) via the parent record and found that when saved, the child record picked up a new recursive number on saving. Was able to remove non updatable field designation and put indexed recursive number back to what it was and all looked OK. Editing of some other child records sometimes did the same thing (created a new number) and sometimes it saved OK retaining the originally allocated number. There was never any error message or bomb out. Re-indexing database seems to have got rid of the issue, which I've not ever experience B4 - and not sure exactly why or how a saved record can generate a new number when edited - no other user was accessing database at same time
Thought it worth sharing this here - any one else experience something like this? Regards Colin Roberts _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
