>Here is my main.prg, can anyone comment on this so I can
>flesh it out better? I am trying to make a .EXE at this
>point. I am coming from the FPW2.6 world, so anything
>that would make my app more "VFP-like" would be helpful.
>I saw somewhere that I should use an application class
>(call an application class?) in my main.prg.
>
>(tabs and s removed)
>
>do setup
>do mainmenu
>do evloop
>do cleanup
>
>Procedure SETUP
>set default to '\\peewee2\dbdev\bftmax98'
> && What is best way to make this ask the
> && user where the data is just one time?
>on shutdown do CleanUp
>set century on
>set mark to '.'
>set date to ansi
>set deleted on
>set multilocks on
>set escape on
>set optimize on
>set refresh to 0,0
>set sysmenu to default
>set talk off
>set view off
>_Screen.Icon = 'DEVCFT.ICO'
>set sysmenu off
>Return .t.
>
>Procedure MainMenu
>Do Menu01.mpr
>return .t.
>
>Procedure EvLoop
> && Is there a better way to show the Splash
> && Screen form and hold it there until the
> && last "noshow" slow-loading form is ready?
>do form Splash
>do form OrdProc noshow
>do form CatBrows1 noshow
>do form CatBrows2 noshow
>do form MaxBar01
>&& Since forms take a long time
>&& to load data sessions, I thought
>&& this might trick them into all
>&& loading at app "boot time".
>read events
>return .t.
>
>Procedure CleanUp
>clear events
>wait window 'Shutdown trap from setup environment' nowait
>clear all
>close all
>flush
>quit
>return .t.

I think you will have better luck with replies if you post this as a new thread in the Coding/Syntax category.

As a start, I don't think many instanciate their forms all at once; only when the user requests them. My splash screen is a class that I instanciate by:

local oSplash
oSplash = newobject("Splash", "AppClass.vcx") && VFP 6 syntax
oSplash.Show()

If your forms use private datasessions, all your set commands are valid for the default DS only. See VFP help on SET DATASESSION for all the set commands that scope to the DS.

Mark McCasland
Midlothian, TX USA