Yes, every item should have a unique ID.

As far as giving you detailed steps... not to be rude, but that really is
your job.  If you work on it and have problems, we can help you out in
specific areas, but it is not very appropriate to say "this is the project I
want to do, design it for me".

To be "un"detailed:

Design your database, design your interface.  Then write code that links
them together.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "PeaCey" <peacey_69@h...>
To: "professional php" <pro_php@p...>
Sent: Friday, April 27, 2001 3:09 PM
Subject: [pro_php] storing solution


> Hi everyone, i have a little scenario, and here it is:
>
> A user logs into a site, they can then a search a database of cars.
>
> What i want to do is:
>
> For the user to be able to pick 10 cars to add to there "Dream List". This
> list will needs to be stored so the user can update it when they change
> their mind. From this is i want them to be able to click on  one of there
> dream car's and see its details again. Also certain members will be able
to
> add new cars of their own to the database.
>
> Im thinking do most of it by the cars and stuff having uniqueid's in the
db?
>
> Im not sure if this is worthy of pro_php, but any help would be greatly
> appreciated.
>
> Cheers,
> Kev
>