Hi Deva;

  No, that would fail as when you move the inherited window from the PFC based App (yes, that would be a manual copy), then it would fail because the PFC ancestors would not be available. Thus editing, compiling & running that window would fail.

Regards ... Chris 

It's likely to fail, as Chris said, due to your PFC descendant window will likely use PFC "stuff".

I the rare case it doesn't, then you might be able to export the pfc window, manually edit the code and replace the "from w_master, or w_sheet, etc" with window ? After that, import the edited file into your non-pfc application.

There isn't, but it shouldn't be as difficult as suggested.  Export the syntax of the window and remove any references to PFC services from the windows events and functions (if any).  That includes any script added to pfc added events (.e.g, pfc_postopen).  PFC events you haven't coded shouldn't appear  in the source code.  In that case, remove not only the code, but the declarations for the event/function as well.   You'll need to point the "inherited from" to a non-PFC window in the existing app.  Try importing it.  If it errors out, correct what you missed in the exported code and try importing again.  Plenty of people have stripped out individual services (e.g., resize) from PFC so it certainly possible with a little patience.