> Hi,
>
> I have a little problem. My customer wants a table with his

articles (approximatly 100.000 records). The problem is : for some
articles , there is no article number. I was planning to design a table
with Article_ID as the primary key. So it won't work anymore. Now, I
guess I have to use a surrogate key, with numbers generated by a generator.
Isn't that a little bit wasted space ? That field doesn't have really a
meaning, but I think it's the only way do do it ?

>

There is no real requiremnt that you need a primary key unless you are
linking in another table for association. However, an integer field used for
a key doesn't waste that much space and saves a lot of trouble later on,
IMO.

Woody