>>Thanks for your help Rick, Jim and Tim.
>>
>>The problem is certainly that the command 'REPORT FORM' inherently has a UI, the popup dialog for starters which counts the no. of pages spooled. It might interest you to know that the same behaviour is encountered when we treat VFP as an OLE server from within VB. Namely,
>>
>>Dim oVFP as Object
>>Set oVFP = CreateObject(VisualFoxpro.Application)
>>oVFP.DoCmd("REPORT FORM 'myReport' TO PRINT")
>>
>>An identical error message is received.
>
>Are you sure? VFP.Application is an OutOfProcess server. What happens
>if you set oVFP.visible = .T.?
>
>+++ Rick ---

Have'nt tried that yet Rick. Will try it and let you know.

Meanwhile I have encountered another problem which I'm sure bears testimony to the fact that I've been playing blind man's buff with some VFP support library DLL's when re-locating my COM DLL objects to another machine, which does not have VFP on it. The support files are, I believe, VFP6r.dll, VFP6run.exe and VFP6enu.dll. The former two need to be registered, which I have done.

All's well when I start a VB app. All objects get created. However, the first time I access one of my components' interfaces, I get an error message 'DLL not registered'. The component runs perfectly well on my machine. (Sure!). I have relocated it to another directory on my machine, and re-registered it. It works. But not on another machine. The error code I get is 'Library is not registered'. Have I missed a VFP support file?

Thanks very much for your help.