>I understand the ease of converting to SQL and the ease of using views. But using views on a local data set has caused performance problems. The client does not want to purge data (we are talk about only two years) and the thought of installing SQL (anybody's) is a little much when difference is how the coding is done. Rememeber using tableupdate(1) on 1.3 million records is causing long delays and using replace/insert is working within a few seconds. How can I justify the use of views?
>
>John
Hey John,
This sounds like a good use for parameterized views. Limiting the records returned by the updateable view should make the update process much faster.