Hi Rich,

>OK my friend; a few pieces of evidence (without being able to specifically address your questions!!).....:
>
>1. generated code from class browser included at the end of this note. From what I can see, it appears that the properties shown *should* have taken care of what I had to use "fudge code" for.

I think you've posted this before. I was wanting to see the class browser code from the calling form, if you don't mind.

>2. some observations of the characteristics of the NEW app as it stands now:
>- there is ONE title bar "Report Designer - Myreport.frx - Page 1".
>- this window CANNOT be moved.
>- when this window is minimized, my app's main window appears- maximized; no title bar.

This is because of the code you posted yesterday and the setting of the preview form's title bar to 0. The app's main window is affected by the THISFORM.TitleBar = 0 and .WindowState = 2. To impact just your preview form, set these properties either in the class designer or by assigning them to the variable returned by CREATEOBJECT()

>3. observations of the characteristics of the app WITHOUT the 6 lines of "fudge code (THISFORM = .....):
>- report designer window appears INSIDE my app's main window.
>- TWO title bars: app's is on top; "Report Designer" beneath it.

First, you can't get around the two title bars until the actually preview window is maximized. Second, I can't understand how, if the caller's ShowWindow is 2 (as top-level form) and this is set as the same it would appear inside the calling form. That's why I'd like to see the calling form's code.

>Is is time to just 'call it a day'... declare this a success (albeit a messy one)... and just go back to our plain old everyday pursuit of fame, fortune and love??? LOL.... Thanks again and have a nice weekend, George!! ...... Rich

Nope, it ain't time to throw the towel in, Rich. My experience has been that the tougher the problem, the more we learn. Stick with it. We'll get it and be the better for it.< g >