>>Well, I'm going to prevail on one of the friendly and helpful folks here again (Ahem!;)...
>>
>>I tried several creating two variations of the print_form sample class, one using a form class and the other a container class. Both included the common dialog. After saving and compiling the classes, I tried to rename the container class. I got the message "Object class is invalid for this container. Class containing OLE object is being ignored. Record #9". Then when I went to look at the class, the OLE object was gone. Now I don't know if the rename had anything to do with that, or was irrelevant to the error. Do you have any idea on this one?
>
>I really don't know what would cause that. Sorry. Are you sure it was gone as opposed to being poistioned beyond the borders of the control?
>
>>One other quick question (I hope). One of the methods in the print_report class which I copied refers to the olecontainer as This.Parent.oleCommDlog.FileName <> "*.*" Would I replace the "oleCommDlog" with the default Ole control name (i.e. it seems to be OleControl1 for the ones whose properties I can view)?
>
>No, oleCommDlog is the proper name for the control unless you've named it something else.
>
>I do have some additional information for you. I opened the sample and clicked on the control, then its property sheet, then the Print tab and...Kaboom. GPF! I dropped a current version of this control on the form and accessed its property sheet without problems (or Kabooms) from the control's property sheet. After looking at the Print properties, with a view of the context of the form, I would guess that there aren't any setting for this sample other than the default. BTW, I can't locate this particular class in VFP 6.0 to confirm.
>
>hth,

George -

Sorry to be a pain, but where does the the name "olecommdlog" from - I can't seem to find that name reference anywhere other than seeing it in the samples code (I looked in various places in help - side note I get 'an error exists in this Help file - contact your application vendor...blah, blah' at a certain point when I'm accessing the VB help for the control).

I had also tried opening a current version of the control on a new form, and initially I thought..aha..the problem is trying to drop it on a class. But with a few more tests, I again had property accessibility problems, even on a form.

Sylvia