Re: getting values from inserted table
From: Brian Henry (brianiup[nospam)
Date: 03/12/04
- Next message: mberry: "Opening cursor after closing does not seem to requery"
- Previous message: Mark: "There is already an object named '#CDList' in the database"
- In reply to: David Portas: "Re: getting values from inserted table"
- Next in thread: David Portas: "Re: getting values from inserted table"
- Reply: David Portas: "Re: getting values from inserted table"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Mar 2004 11:21:26 -0500
its a very complex mathamaticl process used to calculate rates for bills,
when a row or rows are inserted we need to automaticly figure out the new
rates and apply them to existing bills
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@acm.org> wrote in message
news:6LadnQ99gqN2RszdRVn-iQ@giganews.com...
> But what is it that you are doing "one by one"? What happens to these
> variables once they are assigned. Row by row processing should be avoided
> wherever possible and if you explain what you are doing maybe someone can
> show you a set-based alternative.
>
> --
> David Portas
> SQL Server MVP
> --
>
>
- Next message: mberry: "Opening cursor after closing does not seem to requery"
- Previous message: Mark: "There is already an object named '#CDList' in the database"
- In reply to: David Portas: "Re: getting values from inserted table"
- Next in thread: David Portas: "Re: getting values from inserted table"
- Reply: David Portas: "Re: getting values from inserted table"
- Messages sorted by: [ date ] [ thread ]