HI everybody.. need help on my database normalization design...

we have 2 tables which has many to many relationships the first has this fields

clients
CLIENTID CLIENTNAME
1 A
2 B

second table

pubblications
PUBID DESCRIPTION
1 PUBA
2 PUBB

these two has many to many relationship since client can have many pubblications and pubblications have many clients

I MADE A JUNCTION TABLE TO DEAL WITH IT...
table name clientpubs
the fields for the junction are
CLIENTID AND PUBID

MY PROBLEM IS IF it is possible to add more fields to the junction table for tyhe subscription like COUNT AND LANGUAGE or is it better to make a details table tab will INCLUDE
CLIENTID
PUBID
COUNT
LANGUAGE
ETC

thanks
alex

yes, it is

I do wonder why you want a count field though...
Note that Cont is a reserved word too!

if adding more fields to a junction table is alright like count etc... which would be better to add more fields or to create a another table detailing the subscription detail with the following fields?

CLIENTID
PUBID
COUNT
LANGUAGE
ETC

add more columns -- the additional table is unnecessary overhead

Just think - is this 1:1, 1:M or M:M - and bingo - there's your answer

thanks georgev i overlooked that count is a reserved word so i have to rename it..

while for rudy so will be adding fields to the juntion table for the many to many relationship and for the primary key will it be the composite of CLIENTID AND PUBID OR WILL it be better to create a primary key column with type numeric?

composite.

thanks will try that..