OLEpublic classes have no visual interface. In order to provide a visual interface you write an application in any language that can call an automation server (VB,VC++,VFP,Delphi) and put the visual interface there while accessing the automation server to perform certain NONVISUAL tasks like accessing databases, doing calculations, changing system settings, etc.

>>the automation server with their program, VB for example, make the necessary business selections visually from my automation server, then manipulate the RETURNS as necessary.
>>>
>>>TFISHER
>>
>>Terry,
>>
>>Basically the only difference using a visual class is that you have to open the class info dialog and click on the OLE Public dialog for any class you want to expose via information. If the class is being used internally by the COM Object then you won't need to do this.
>>
>>Project settings will be the same with .PRG and .VCX classes.
>>
>>BOb
>
>
>Hi Bob,
>
> Let me see if I understand. In order to create an Automation Server with a visual interface, I create a project and in that project, I create the necessary data classes, form classes, etc., just like I was creating a stand-alone application. Next, if I have a form that has some custom properties that I want to expose to others, I need to make that particular form OLEPUBLIC. I do not have to make all other classes OLEPUBLIC. Finally, I build the project selecting the Build .EXE setting.
> Assuming I have correctly followed what you are saying to this point, my next question is how do you call and run the visual application after you have built it? I did something similar to what you are suggesting, but, I made each of my classes OLEPUBLIC. After I built the .exe, I checked the Registery and each class was listed. When I tried to run the application via oTest = CREATEOBJECT(), my computer got hung up and I could not do anything except stop the process on the .exe. (NT4/SP3)
>
>Thanks,
>
>TFISHER