Jamie,

I haven't investigated the cause of the problem. At that time I was only interested in a good result.
Later I started thinking that the problem could be related to the views itself. All the views I have are 'updatable'. I assume that when using these views for reporting this property somehow gets in the way. My solution was not to use the view itself but to execute the view-sql into a cursor. For some reason that does not give the speed degradation.

An other solution suggested to me by a client was to create two databases: one containing the data (on the network) and one containing the views (residing on the users machine). This scenario also does not show this problem.

Running the app more than once on your does not give the problem is an interesting issue. When testing our apps we tested multi-user and still we did not run into this problem. I started running into it when a user starting to mass-print while someone else was modifying. The moment they got in each others way the reporting performance dropped from 12 seconds to 15 minutes and up. The cursors have now soved this and I have no problems anymore.

Regards,

Ron Brahma