That's interesting. I was under the impression, of course I may be misinformed, that, coding aside, a VB EXE would be smaller than a VFP EXE with the same number of forms and controls per form and has a smaller memory footprint. I was under the impression also that this was one of the actual technical reasons for using VB as the front end of an n-tier app.

If you, or anybody, can clarify this for me it would be most appreciated.

>Hi Colin
>
>I don't have any metrics on it, but I have seen a situation where a VB app with about 20 forms and about 30-40 controls per form create an EXE that caused all sorts of memory problems.
>
>
>>
>>How much of a pig? I'm seriously asking this question because I don't know. Also, because there have been a few threads here, that I've taken part in, about running VFP applications over Citrix and one of the biggest concerns was that because VFP's GUI is one big bitmap the whole thing has to come down the pipe with every change rather than just the object that changed.
>>
>>>Hiya ---
>>>
>>>>>Real Windows Control (buttons, toolbars, checkbox ,etc) and GUI interface.
>>>
>>>No no no no no, you DON'T want that. Ever see a VB application with a lot of forms and controls? It's a pig, because each control is it's own little Windows object.