Mike Yearwood
Toronto, Ontario, Canada
General information
Category:
Coding, syntax & commands
>I've been using remote views primarily. I can use SQL Pass-thru and I do for executing stored procedures on MS-SQL Server. So what's the advantage of a remote view that SELECT * FROM TABLE over an SPT that does the same command?
>
>Is updating tables using SPT faster than updating using remote views?
>
>How does optimistic/pessimistic buffering affect performance in updating large #'s of records?
>
>Is there a set of guidelines to follow in determining which approach to take per scenario?
I'll let you in on a secret... Remote Views are just a wrapper around SPT, and actually USE SPT to get the data. If you run GENDBC of your database, and looked at the code which created the Remote Views, that is basically what is happening when you use a remote view... A connection is opened, the SQL Is passed to the back end... then, abunch of CursorSetProps are run against the cursor to make it updateable, if that is how you set it up.
I would recomend Remote Views for your standard data maintenenacne forms, and SPT for queries, lookups, validations, stuff where you will need to build or specify the where on the fly.
BOb
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only