>>>>Is there a way to completely mask any indication in the user interface that an app was developed with Visual Foxpro?
>
>>>In your congig.fpw set SCREEN=OFF,
>>>Set _screen visible to true after you changed the title.
>
>That sounds like a clever idea!
>
>However, if I just do the suggestion below (which I've already tried), there is still a "Microsoft Visual Foxpro" visible on the title bar of the main app window until these statements in the app are actually executed:
>
>>If you've got VFP v.5, try this:
>>_Screen.Icon =[D:\vfp\myicon.ico]
>>_Screen.Caption =[Mark's Program]
>>_Screen.Visible =.F.
>
>However, I've never experimented with the ShowWindow property as Joy suggested. If I set the main form's ShowWindow property to As Top Level, then what happens to the "classic" interaction of a form with the main VFP window... that is, are forms now required to interact differently with each other or with the menu bar?

I mostly use button-driven screens, instead of menu bars. However, I can tell you that the only time that I've had a problem with top level forms is with previewing reports. then you have to make the _screen visible, print the report (preview), then maximize _screen. Like this:
_SCREEN.Visible =.T.
_SCREEN.Windowstate=2
REPORT FORM Rep_auth PREVIEW FOR Aut_head.Aut_no <>" "
_SCREEN.Visible =.F.
It seems to me that if you make your menu in the top level form, menus would behave as well as forms do. Also, it just looks better. You literally can't tell what it was written in. Also, the user can move the windows anywhere on the desktop, not just within the big ol' white screen. Give it a go. It really looks professional. (By the way--there's a knowledge base article on this, which is where I got the idea & modified it for my own needs).

JR