>I advise against using those values for primary keys. Use an Identity field instead and store the imported values in an indexed column.
>
>>Hi, is ther any restriction or best practices on using '' "" on primary keys or codes? we are about to import some data to a sql server database, these codes and / or descriptions have '' or "" on them and i am concern about the behavior of the system when querying data
Thnks for the advise, i surely will take it in consideration. do you have any experience (bad or worst) when using these kind of chars for advising not to use them in PK?
.......
DO WHILE .T.
ME.Work()
ENDDO