>George,
>I
>t may, but if the server is runing on a different machine (DCOM) then you would have a message box on that machine that the user can't see and can't dispatch. Basically your server is hung. That's why UI is not allowed in DLL (Out of process) servers. EXE (in process) servers can us UI.


Wait a minute... isn't a .DLL ole an IN-Process server, and an .EXE an out of process server?

Yes... from the FoxPro Doc:

********
In Visual FoxPro, you can create either an out-of-process or an in-process Automation server. An out-of-process component is an executable (.exe) file that runs in its own process. Communication between a client application and an out-of-process server is therefore called cross-process communication. An in-process component is a dynamic-link library (.dll) file that runs in the same process address space as the client that calls it or in a Microsoft Transaction Server process.


User Interfaces and In-Process Servers
The new apartment model threading support requires that in-process .dll Automation servers not have user-interfaces. In Visual FoxPro 5.0, one could create (although it was not recommended) an in-process .dll Automation server that had a user-interface such as a form. The form could be used only for display because the form events are not supported. In Visual FoxPro 6.0, any attempts to create a user-interface in an in-process .dll Automation generates an error.

An out-of-process .exe Automation server can have a user-interface. A new Visual FoxPro 6.0 function, SYS(2335), has been added so you can disable modal events for an out-of-process .exe Automation server, which may be deployed remotely without intervention from a user. Modal events are created by user-defined modal forms, system dialogs, the MESSAGEBOX( ) function and the WAIT command, and so on.

*****************
BOb