I have a table with about 12k records and 90 odd fields. This is the way it has to be so please don't talk about normalisation. It has nothing to do with this problem.
I have extracted data from this table to a smaller table for the purpose of creating records.
One of the fields has some entries but is, for the most part, empty, I.e. null.
I was having a problem with a couple of double ups in this small table and found if I sort on the empty field, [Infra], the four double up records appear at the top of the table. The same behaviour is evident in the main table with these, and a few other, records. If I copy one of these records and paste it into the small table the copied record exhibits the same behavior.
I have attached a sample of the table.
If you sort on any field other than "Infra" all is normal. if you sort in Infra, "A to Z", and look at the "Family" field you will see the four records in question.
This is most obvious if you sort on "Family" then "Infra".
If I delete the "Infra" field then reinsert it in design the problem disappears.
In the main table there are 8 records, entered in sequence, displaying this same behaviour. Records before and after this group appear to be normal.
I have extracted data from this table to a smaller table for the purpose of creating records.
One of the fields has some entries but is, for the most part, empty, I.e. null.
I was having a problem with a couple of double ups in this small table and found if I sort on the empty field, [Infra], the four double up records appear at the top of the table. The same behaviour is evident in the main table with these, and a few other, records. If I copy one of these records and paste it into the small table the copied record exhibits the same behavior.
I have attached a sample of the table.
If you sort on any field other than "Infra" all is normal. if you sort in Infra, "A to Z", and look at the "Family" field you will see the four records in question.
This is most obvious if you sort on "Family" then "Infra".
If I delete the "Infra" field then reinsert it in design the problem disappears.
In the main table there are 8 records, entered in sequence, displaying this same behaviour. Records before and after this group appear to be normal.