Mesa,

Sorry I didn't answer more quickly... I was out of town for a couple of days and 'unconnected' to the web :(

Anyways, here is some more information:

You said,
>So what about using API,...or using VB?

>I'm still wondering about which library would come first when an instance of
>Visual Foxpro (application) is loading,...
>Is it Foxpro's own library first or Windows' Library,..?
>Tell me about it,..!!

Well, the main point is that you want something that that "gets going" faster than the first screen of your VFP application. Visual Basic is a good choice - the first screen in a minimal VB app will alway display more quickly than the first screen of a VFP app. So here's what you would do:

Create a new VB application (choose the "Standard EXE" kind) and play with the default form that you get until it looks like the splash screen you would like. Double click on your form and insert code in the form's "Load" method to run your VFP app using the "Shell" statement. (something like this:)

Private Sub Form1_Load()
Shell "C:\Mypath\MyApp.EXE -T", 1
End Sub

(Include the "-T" on the line above to stop the regular VFP start-up screen from showing)

Close that code window, then put a timer control on your form. Set the "Interval" property to 5000 (for a start - this will give you 5 seconds) and double click on the timer control to see the empty "Timer" method. Fill it in like this:

Private Sub Timer1_Timer()
End
End Sub

These are just the basics. I suggest you use a "Config.fpw" file in your VFP app to tweak the results even more - also, try different values in the VB timer's "Interval" property.

HTH,

-Bernie