>I was referring to that fact that MicroSoft obviously seems to be favoring VB over VFP.

Yeah! It's obvious but it doesn't mean VFP is an inferior product over VB or vice versa. If you know the strength and weak points of each products and then use the right tool for the job. MS markets VFP as middle-tier tool for Data Intensive Components. Your concerns are the same I've seen on some VB threads. Meaning, VB or any tools aren't excuse when it comes weird problems.

>
>>>The question is: is it safe to write DCOM objects in VFP, or is the VB environment a safer platform?
>>
>>I'm not sure what you mean by safer, but I am confident that the answer is no, VB is not 'safer'.
>>
>>>First, VB appears to be the favored development environment.
>>
>>Favored by whom? If this is a real concern for you, then I guess your decision is made? IMO, you should use the tool that you deem best for the job, not the tool that some marketing dork deems best for the job.
>>
>>>Second, I have heard that Foxpro uses non-traditional aggressive memory management techniques.
>>
>>VFP is very memory hungry (thats part of why it is so fast) and will use as much memory as you allow it, but you can configure this with SYS(3050).