We've done so, but with mixed success. The interface used a treeview control from which users selected records to edit. We (and our users) really liked this interface, but the performance for a few of the views (they were important) was unacceptably slow, even after users filtered unwanted data. Some of this was due to architecture. The application originally was designed to operate as a stand-alone. We moved the application to Terminal Services and later re-architected the population of the treeview nodes to be dynamic. We are now very pleased with the performance of the application.

Some things we've learned through this process include limiting data fetches to exactly what is needed, using arrays and cursors for temporary data storage instead of temporary tables (to avoid any I/O performance hits) and having indexes that match the expressions in SQL WHERE clauses.

Hope this helps,

John