I have a table which, sometimes, when I reload the database I am told that it cannot have duplicate rows. Now I know that sometimes is impossible but, believe me, it happens.
It happened again today so I looked at the table again and output a backup to a file and examined that. Nothing obviously wrong so I ran the file to replace the table (deleting the original first). It loaded and created the PK with no problem. I then look at the table in the designer and noticed that the 3 columns in the PK were sorted ASC whereas when I defined then two were ASC and the middle one was DESC. The designer allows this to be done. (The middle column simple specifies "header" or "footer" and I prefer "header" to come before "footer" - no other reason.) I then looked at the output file again and noticed that neither ASC nor DESC are assigned to the PK definition. I then checked R:Syntax and that doesn't appear to give any option to define the sort for a PK at all. I then deleted and tried to create any 3 columns with a DESC sort as part of a PK and some combinations would work and others would not accept it. Now I don't understand how there can be no duplicate rows if the 3 sorts are ASC and sometimes there are duplicates if one column is DESC. I then connected a backup copy of the same database and looked at the definition for that table and the middle column is defined as DES and the other two as ASC. The backup was made just before I tried to reload and got the error message today. Oh, by the way, there are only 100 rows in the table and it is very easy to check for duplicates and there are not any. Should I be able to choose the sequence or has something changed recently? Regards, Alastair. ---------------------------------- A D B Burr, St. Albans, UK. ---------------------------------- [EMAIL PROTECTED] ----------------------------------
