I am using the DE and I have alot of tables and views in it. So its better to remove them from the DE and issue use statements in the load for each of these tables and views?

I use the property sheet now to set table buffering etc...I guess I would just use cursorsetprop for table buffering? Is the nodata parameter to the use command the same and NoDateOnLoad in the property sheet?

Also, my view is based on one of these very large tables. I have both the View and the table in the DE. The reason I have the table in there too, is because I needed table buffering on this table. Because I found that as the record pointer moved in the View changes were committed to the base table so I also needed to revert the table as well as the view if the user cancelled out of the form.

Does this sound correct?

Thanks
>Paul ---
>
>Perhaps you could try opening the views before instancing the forms? This would give an apparent speed increase....or, get rid of the DE (if you are using one) and open the views in Form Load.
>
>
>>No, the rowsource for my grids are views and I am using NoDataOnLoad set to True. I have textboxes on the first tab of a pageframe that are bound to a table but that table only has 20,000 records. I have 2 views one based on each of the very large tables.
>>
>>>Hmmmm.......Do you have any grids, listboxs, or comboboxes where the rowsource is one of the big tables? That could be the slowdown. You could use views with NoDataOnLoad set to True, and then selectively requery.
>>>
>>>>I have noticed that my form's instantiation speed is determined by the size of the files in the data environment.
>>>>
>>>>I have a form that has a table with 350,000 records and another table with about 200,000 records. When I issue the do form it takes 15 seconds for the form to load. If I zap these tables then it takes about 4 seconds.
>>>>
>>>>What is happening here? Is there some setting I can set to speed this up. I don't think my customer's are going to find this acceptable.
>>>>
>>>>Thanks,
>>>>Paul