>>
>>OOish way is to create 'application' object based on custom class with set of properties and methods. These properties will work as FPW public variables and methods will perform role of system procedures.
>
>another thing you can do (writing an application object is recomended but this is regarding the "public vars") is to create a cursor (or use a table) that will hold such things and have each class check for the availability of this table and update internal properties to the values there (if the table exist )
>
>Arnon

Arnon, you're a genius. I've been grappling with this public thing, and have created some classes to hold the info, but the cursor seems clearly superior. After all, it's the way it's done for the MAPI classes.

Thanks.