Table design question

[JB]

I have a table for recordings, a table for playlists, and a table for
playlist details, that uses the primary key from the recordings and playists
tables as its primary key.

I would like to develop playlists quickly, by just typing in the
information, and not selecting recordings from the recordings list.

To accomplish that I set up a default recording, recording ID#1, and tried
to put this on the playlist, the problem is that access will not allow it to
go on multiple lines.

Any suggestions?

[Pieter Linden]

Re: Table design question

"JB" <imkazaam@nospa m.com> wrote in message news:<10cp2imo5 lngf7f@corp.sup ernews.com>...[color=blue]
> I have a table for recordings, a table for playlists, and a table for
> playlist details, that uses the primary key from the recordings and playists
> tables as its primary key.
>
> I would like to develop playlists quickly, by just typing in the
> information, and not selecting recordings from the recordings list.
>
> To accomplish that I set up a default recording, recording ID#1, and tried
> to put this on the playlist, the problem is that access will not allow it to
> go on multiple lines.
>
> Any suggestions?[/color]

Maybe you should re-read your own post. The source of the problem is
almost painfully obvious. Your PK of (RecordingID, PlaylistID) means
that the database disallows duplicates of that pair, so you can't add
the same recording to the same playlist more than once. So choose
another primary key combination or use an autonumber...