>>I have a software for blockbusters
>>
>>Suppose there are two films with the same name
>>The customer has a button in the for to help him
>>to create a new record without the work of typing all data again
>>So a new record is created with new code, as below
>>
>>00101 - TERMINATOR
>>00102 - TERMINADOR
>>00103 - TERMINATOR
>>00104 - TERMINATOR
>>
>>Now I have a customer who is complaining about my software
>>
>>He said the software should work as below
>>
>>00101 - TERMINADOR; quantity 3
>>
>>I don't agree with his logic but I have a doubt
>>What do you guys think would be the normal logic for
>>most blockbusters ?
>
>If I were designing this database, I think I'd have one table for a master list of films and a separate table identifying the copies of that film owned by that store:
>
>FILM
>
>iID -- primary key
>Title
>other identifying information
>
>
>STOCK
>iID -- primary key
>iFilmID -- foreign key
>dAcquired
>any other identifying information for this copy
>
>In the user interface, then, I'd be able to show a summary for each film or the individual copies.
You got that right. Computing 101 - How to build a video store system.
http://www.databaseanswers.org/data_models/