Hi, I’m working with Phoenix 6.3 (64bits). When i try to import pwo or pmo files generated with WinNonlin v5.3, i have the following message: FILE.pwo (or pmo) has an extension that’s not supported in 64bit. Would you like to import as a Binary Object? Yes / No buttons If i click on Yes, then i have a file that goes under Documents file but i can’t used it for NCA or plotting function. How can we import old files into the new version ? Thank you, Ed
Hello, To load .pmo and .pwo files (as well as any other type of WNL legacy file) you need to use Phoenix32 (32-bit). This is available in the same folder where Phoenix is installed. You can import those files, save the project and then that project can be opened in the 64-bit version. Here is also an extract from the release notes. 64-bit version of Phoenix (QC 9748, 11064, 11144, 11145, 11175, 11188, 11418, 11419, 11420, 11421, 11422): Phoenix 1.3 can be deployed as a 64 bit or 32 bit application. For 64 bit systems, the installer will install both Phoenix 64 bit (Phoenix.exe labeled in the title bar as Phoenix64) and 32 bit applications (Phoenix32.exe). Phoenix64 is the default that is loaded when selecting Phoenix from the Start menu. Phoenix64 is intended to allow the software to use more of the available memory on the system and not necessarily improve performance. The 64 bit version results have been confirmed to match 32 bit version results. The Phoenix 64 bit version can also be executed via the command line and remotely via the Job Management System (JMS). However, there are some features that can only be performed by a 32 bit application, these include: • Import WinNonlin legacy files from versions less than 6.0. For example, .pwo, .pco, .pto, .cmd. etc. • ODBC imports • SigmaPlot object cannot be executed • Autopilot Toolkit for Phoenix is not available in Phoenix64. If the user necessitates any of the functionality above, Phoenix32 should be utilized. Note that Phoenix32 can be used to import WinNonlin legacy files and ODBC and then a project can be saved that can be opened in Phoenix64 to continue the workflow. Phoenix.exe (i.e., the Phoenix 64 bit executable) will still run on 32 bit operating systems but as a 32 bit application.
we are running version 6.3 as a 64 bit and a client cannot open the files with version 6.2 is this something you can assist with?
Elliot, I’m just trying to clarify your question; you want to open an analysis performed in 6.3.x in version 6.2? If so this workaround may work; export the raw data (from the data folder of the XXXX.phxproj in the LATER version) and also the workflow as a template; remember Datalinks! then you can try and import both into an earlier version of Phoenix; however if the original 6.3 project workflow had objects that 6.2 does not e.g. a data wizard then the chance of it opening are minimal. I’m sorry for this inconvenience but as I am sure you can imagine maintaining forward compatibility is somewhat difficult whilst adding new features to the software. Simon.
Hi Simon, precisely, I have 64-bit version 6.3 and sending the project to a client who has version 6.2 32-bit and they are having difficulty opening the project. I appreciate the challenge in forward compatability but you had cross-compatability in versions 5-5.3 and there wasn’t any issues for us but only 0.1 version difference and we are having challenges.. The project literally only has an 1 data file and a single NCA object I’m not sure I understand the workaround you described. can you provide a model detailed approach. Thanks Elliot
Elliot, I understand your frustrations and spoke with our Support group to see what other suggestions they might have for you and here I summarise the options; 1) . a)Right-click → Export to save those worksheets you need to recreate the analysis e.g. raw data and Final parameters, NCA Settings text output b) import those into PHX 1.2 2) For the future it may be useful to maintain a validated Phoenix 1.2 installation somewhere at your site, and use that machine whenever doing work for a client that is still using Phoenix 1.2. (I completely agree that this is not optimal) >> another option might be that your client installs 6.3 on a ‘spare’ machine and simply opens your project to view it; note that you can open projects in unlicensed copy of Phoenix so no extra cost and I would think to view an analysis they wouldn’t need to validate it. 3) I am not sure that exporting workflow templates from PHX 1.3 → PHX 1.2 will work in more complicated but if you want to try it these are the steps I would take; a) Right-click → Export to save those worksheets you need to recreate the analysis e.g. raw data; I would also supply the the Final parameters.csv and the NCA Settings text output b) if you haven’t already put data links in your workflow I would recommend to do so before step c. (see Certara | Drug Development Solutions for a discussion on these) c) Right-click on the root workflow → Export as *.wnlt d) optionally Zip up the data files and WNLT e) send the client the Zip f) client (6.2.x user) unzips the files first, g) creates a new PHX project & imports the data files and WNLT h) connect the source data to the data link in the Workflow i) Execute the workflow - should be the same results as you had in 6.3 Sorry I can’t give you a more universal/succinct solution Simon