Thanks Doug & Jason for your ideas!

The delay occurs actually during the bizobjs' instantiation. I can see all the query messages in the status bar on the bottom of the screen (0 records in 1 sec here, 0 sec in 2.5 secs there, and so on).

Looking at vfp's help I read that even though you use the nodata clause, the query is indeed executed. The only difference is that in this case vfp makes sure that the parameters result in an empty recordset.

I'll do some testing with the profiler once I'm out of the storm.

Thanks again!

Alex


>Alex,
>
>I totally agree with Jason, but I would also add that you should run the coverage profiler on your form's initialization to see exactly what is taking so long. Make sure your form is fully optimized, loading of data, etc...
>
>In other words, make it as fast as you can, and then try to delay the instantiation of controls on pages until necessary.
>
>HTH
>
>>Hi!
>>
>>Is this at all possible? I think I found out why my forms take so long to instantiate the first time I run them.
>>
>>Even though the nodata clause is used for bringing the views in the bizobjs online, some querying does take place (acording to vfp help).
>>
>>Is there a way to delay this until I REALLY need the view to be activated?
>>
>>That's where the title of this thread comes from.
>>
>>Some of my bizobjs use rather complicated views that take long to even return an empty cursor and I think this is what's causing my forms to appear sloppy.
>>
>>Thanks!
>>
>>Alex