If you are using the "Default value" to generate your unique ID in your DBC, I can tell you that when I did APPEND BLANK it gave me the "uniqueness Index" error. I had to use INSERT INTO ... and it works like a charm.
Why? - who knows...
Does it append a blank record and then tries to replace the primary key field with the next ID code and thinks that someone is using the record? - again, who know...
>Nope, I'm using a straight ole "append blank" here because the code in this section is very generic. I could write a case statement for all of the screens and use that to create an "insert" statement with fields and values but it seemed easier (?) to append blank and then replace.
Work as if you don't need money
Love as if you've never been hurt before
Live as if this is your last day to live
Dance as if no one's watching
