>>>>I have made a basic VFP 5 COM Server.
>>>>Its services are used by a VB 6 front end.
>>>>
>>>>The VB 6 programmer tells me whenever the COM Object is being used by his VB 6
>>>>program the MsgBox commands get skipped.
>>>>
>>>>The messages boxes simply do not get displayed.
>>>>
>>>>He has worked around this problem by displaying his own custom made forms rather than using the MsgBox command.
>>>>
>>>>Am I doing something wrong?
>>>>Are there compiler settings I am setting incorrectly when I build the .dll file?
>>>>
>>>>My code is a single .prg file containing DEFINE CLASS OLEPUBLIC ... ENDDEFINE along with the properties and methods of the COM object.
>>>>This single .prg file is the 'main' file of the project.
>>>>
>>>>TIA
>>>
>>>Hi Dave,
>>>
>>>Do you mean just any MsgBox command in his VB6 project fails? I used VFP 6 COM object with VB 6 form and didn't have any problems with VB MsgBox command.
>>
>>
>>It skips past the MsgBox command as though it does not exist.
>>No errors are reported.
>>
>>I am concerned the VB6 programmer does not know what he is doing and there are other settings he is not working with properly or something...
>
>Is it possible to test the same VB routines containing MsgBox without instantiating the COM? Or may be place additional button calling some MsgBox and see what happens?

this has been done.
When the COM dll is not in use the MsgBox command works as expected.
When the COM dll is not 'created' the MsgBox command is skipped.

I guess I am going to make my own VB form and try to recreate this error.
The COM dll I made can easily be ported to VFP 6.
So I may try using VFP 6(SP4).

I was really wondering if anyone else had a similar experience with a combination VB6 front end and a VFP5 COM/dll server.