No matter how you solve this, stay away from general fields! General fields seemed like a good idea many years ago, but they have turned out to cause much more problems than they solve.

>Hi, I wrote a class that creates an object and stores all demographic info into its properties.
>
>Example:
>accountInfo=createobject("demographic")
>then on reports I refresh the object for every record and I put on the report:
>
>accountInfo.nameE
>accountInfo.nameY
>accountInfo.dob
>accountInfo.addressMultiLine
>accountInfo.parentsName
>Etc.
>
>I find it very clean as opposed to using variables.
>The real reason was cause some times I need in the same record, info for 2 different accounts. that's in a Partner report. We want to see all Demographic info for Partner 1 and all Demographic info for his Partner.
>So I have in the running cursor 2 fields for partner1 ID and partner2 ID
>and I instanciate 2 objects
> accountInfo1=createobject("demographic")
> accountInfo2=createobject("demographic")
>and I use both objects simultaneously
>
>Now Question:
>
>I would like to store the Class Objects into gen fields before the report runs instead of calling it from the report.
>
>Is there a way? What type of classes can be put in a gen field? OLE? whats that? how do i make such a class.
>
>Thanks