2. UpdateSQL does the same as a normal ExecSQL.
3. Use an UpdateSQL if the changes to a cached dataset can be applied with a
single SQL statement. If you need more than a single update or if you don't
want to use caching you should use a query (or a live dataset).
4. Good: very little work. Bad: changes are applied AFTER a post, so the
user can't have direct feedback if the post will be successful.
Quote:> Hi all,
> please explain me differences between UpdateSQL component and
> SQL line which I wrote in Query and execute by my own.
> I need to know:
> 1. Differences between ApplyUpdates in UpdateSQL component and ExecSQL
> in Query ?
> 2. Does UpdateSQL component do additional operation when collecting
> and applying data ?
> 3. When better use UpdateSQL component and when Query.ExecSQL ?
> 4. Good and bad thing in UpdateSQL component and Query.ExecSQL ?
> 5. ...
> Thanks.
> Ernikas
1. Setting up an UpdateSQL component at run-time
I know it is possible to manually set the DeleteSQL, InsertSQL and -- Sent via Deja.com http://www.deja.com/
ModifySQL properties at runtime. Is it possible to do a generate SQL at
run time like you can at design time, to automatically set the Delete,
Insert and ModifySQL properties.
Nice One! Sorted!
Before you buy.
5. What is differences between object and component?
7. Difference between dynamic sql query and a normal query
10. BCP query out executed by xp_cmdshell works fine from query analyzer but fails from VB Component
11. Using UpdateSQL for updating cached records
12. Problem - UpdateSQL with Paradox