>we have a table that has the id field (cid) set as primary. The primary key generating code starts with "000001" and increments thru "000009" before changing to "00000A". When it has incremented to "00000Z", we will get the "Uniquiness of CID is violated", but the primary key value that it is trying to save is "00000a". We have many other files (170) that are all set up like this and they are not having this problem. It is driving me crazy! Why is the case being ignored?
Sounds like the problem is in the code that generates the PK. Can you post it?
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer