Bioequivalence and Bioavailability Forum

Hi Balaji!

❝ why not phoenix winnonlin not opening pwo, xpt and other winnonlin files by click it on its icon

In Windows opening files by (double!)clicking on its icon requires an associated default program. The as­so­ci­ation is set during installation. Therefore, *.xls(x) opens in Excel, *.doc(x) in Word, and *.xpt in SAS. You can change it later on (e.g., opening *.txt instead by notepad.exe by excel.exe). I don’t have SAS, but defined the association of *.xpt to open in Stat/Transfer.

(Classical) WinNonlin-files (*.pmo, *.pwt, …) are binary objects, which are linked to others. No way.
*.xpt (SAS transport) are flat files, but also binary.
Phoenix projects (*.phxproj) are zipped containers. Try it with one of yours: Copy it to an empty folder, rename it to *.zip, and uncompress. You will get an endless list of *.data, *.object, *.index, *.xml… The files are pass­word-protected (xineohp). Doesn’t help because (with the exception of *.index, *.xml) they are binary as well.

❝ but it can be opened by import it after starting new project

Works as designed. Given that even a new (empty!) project contains already 11 files defining it’s structure, linking to a single one will never work. You want e.g., the content of SAS.xpt as a new object linked at the right place within the project:

Therefore, importing is the only way to go.

It is not possible to directly import WinNonlin-files in the 64-bit version of Phoenix. However, it works in the 32-bit version. If you want to use the 64-bit version of PHX (recommended: speed and no memory limitations):

• Start the 32-bit version (Phoenix32.exe) and generate a new project.
  
• Import the legacy file(s). Even workspaces are supported.
  
• Save the project.
  
• Close PHX.
  
• Open in 64-bit Phoenix (Phoenix.exe) and save.

Details: …\Program Files (x86)\Pharsight\Phoenix\docs\Phoenix WinNonlin 6.4 Release Notes.pdf, Section “WinNonlin^® 5.x to Phoenix^® Transition”.