>>>< SNIP >
>>>>I know, and I already have a class which does that - creates temp filenames, keeps them in an array property and deletes them on destroy. This time, I had a feeling that I could completely avoid the disk. It didn't seem natural that a form should communicate with an object it contains using external files - unless the object was an entirely unfriendly OCX.
>>>
>>>I was under impresseion that there is unwritten rule in VFP: "Any OCX should be treated as hostile until can be proved otherwise". <g>
>>
>>:)
>>
>>My approach is slightly different: "any OCX is a wild animal; some can be tamed."
>
>
>Those from DBI migh be an exception to the rule, but I haven't really begun to tame them yet...

These animals are like a dogs or cats - they require little effort to tame, just because made specially for VFP.