>Kevin,
>The rv's for an as400 ARE slow to load. Each one can take between 5 -20 seconds even if I try it as you suggested from the command line with the nodata command. Some the reports I create require 12-14 views to get all the information needed. Part of the reason the connection is slow is that the as400 programmer has put our ODBC connection to a batch status so that we don't interfere with active users. This was necessary because when I originally starting doing these reports the ODBC would grab all the as400 resources and freeze the user input screens. With batch status no one notices that the reports are being run. I now have 7 users that access these reports. Some are here in our LA office, and some coming in across a frame relay from Nevada (the as400 access across the frame relay is reallllllly slowwww.)
>
>I haven't worried about the delay before because instead of using bizobj's I was calling the views from a program triggered by the click event, so the delay was after the user interaction. Now I'm converting the reports to an MM project and giving the views bizobjs & data sessions to manage them. In the project they are loading without data (the MM default) and when I need them I requery.
>
>These views aren't being edited, they're being used to gather information for reports. Would it help if I put an event object for the reports on the form and then had the event object load the bizobjects after the user has entered the required parameters, or does the event object call the bizobj's when the form loads?...which would mean the user delay is still there.

I ran across a similar situation with an HP 3000. The administrator was afraid that the ODBC driver would slow down the transaction processing. (It was a load of bull, but the odbc process got bumped to a lower job que.) What I finally did was create a datawarehouse with MM! I used my remote views to populate the warehouse every night. The night operator ran the job after the backup, but you could easily write a script to run the exe. It didn't matter if the data was one day old, and the load was fast because mine was the only job running on the box. (Also, no network IO) If I needed uptodate data, I had the option of running individual updates from the server, or simply using a combination of remote and local views. MM is perfect for something like this. We eventually built the warehouse with SQL Server 7.0. If you need more info, let me know.