>>to all
>>i have a very basic vfp6.0 .exe that simply opens a small table for data entry. the form was created using the form wizard. when i run this as a shortcut from the win95 (start/run) desktop it takes approximately 15 seconds for the form to become visilbe on the desktop for use.
>>
>>if i run it from within vfp6.0 it takes a couple of seconds.
>>
>>in both cases the application runs fine but it takes what seems to be forever to startup as a standalone.
>>
>>i'll take any suggestions on ways to speed up startup of the .exe.
>>thank you
>
>I get about 5+ seconds to get to the first "interface" {no splash screen here} in a networked exe. That would be a login screen where the user logs in.
>
>P 200 with 96 meg of ram. 100 mb nic and backbone to Novel server 3.2 {server is a P166 desk top machine with 128 meg of ram} 15 users currently attached and no one is using this app today.

My apps are more like 10 seconds with network exe and data from desktop and vfp closed, and around 5 seconds when in vfp with same network stuff. The odd thing is when I run from desktop icon with vfp open, it takes longer, a good 15 seconds. There's probably a rational explanation, but I don't know what it might be...

You bring up a good point, and that's that one way to speed the loading up is to have a simple login or entry screen, without much data load. You then have a two-step process, part for DLL loading, etc, and part for the heavy data/object loading, producing a net effect of a faster app to the user...