How you define user objects for an automation server depends mainly on your application design. The object must be a custom class user object. You define instance variables and functions for the object. The object can declare and instantiate other objects for its own use.
No references to visual objects
The class user object you use as an automation server cannot
contain any references to visual objects such as message boxes or
windows.
You can pass your object references to other objects in the client application. Those references are of type OLEObject, and your object can use automation syntax to access properties and methods of the object. (Automation accesses the object’s instance variables as properties.)
Before you try accessing your user object as a server, test its design and functions in a simpler environment. You can build an application for testing the user object locally.
