You have a point.

What i expect is to have a faster access to the stock quantity for each
serial number in the database... i.e.

I m selling a product, instead of making a select sum() on the stock table,
i can just check the products table for the current quantity, and i want
make this using the serial number, for each serial number i ll have a
current quantity thats why i have the second table.

That second table is nothing but the sum of all the records on the other
table wich have a certain serial number, so i dont need to make a select in
N rows, instead i select just ONE value from that table.

Did you undestand where i m trying to get?

thanx in advance,

-Fábio.

On 7/28/06, Alan McDonald <alan@...> wrote:
>
> I think it would be beter if you tell us what you want from this
> procedure
> of updating/inserting. What is the resultant query you wish these actions
> to
> make easier/faster - instead of what you want to implement.
> Certainly you can trigger this action on tables or you can use an
> update/insert SP to do it for you. But I smell some other issues.
> After these actions have been taken, what query do you want to use and
> what
> is the expected answer from it?
> Alan
>
>
>


[Non-text portions of this message have been removed]