The first thing you should check is that the license files are saved in the correct location. The license files should be saved to the Config folder of the PHDWin installation directory. The default file path is:
On 32-bit systems C:\Program Files\PHDWin 2.11\Config
On 64-bit systems C:\Program Files (x86)\PHDWin 2.11\Config
Next, check the file name. The file should be named “PHDWin US.lic”. Some email clients will add underscores in front of the file name that should not be there. Rename the file to remove the underscores and then try opening PHDWin again.
If you still can’t open PHDWin, there is a problem with the registration. Click the Register button in the PHDWin splash screen to open the Registration window.
There is a setting in System Preferences that dictates whether or not that tab appears in Project Properties. To enable this tab,
The next time you open file in PHDWin, your Project Properties should show the Conventions tab.
You cannot Save changes in the Project Properties while other users are in the database. You will have to ask the other users to close the file before you can make your changes.
Sometimes PHDWin will read traces of other users even after they have exited the file. In this instance you can run the Pack option from the File menu to clear out those traces of other users. After you Pack the database, you should be able to Save changes to the Project Properties successfully.
First, note that in the Global Editor, at the bottom there is a Find button. By clicking this and entering a keyword for what you are looking for, you will be taken directly to that topic in the Global Editor, which is much easier than having to look through all of the tabs. If you check the “Use comments” option, it will also search the help text on each available field in the Global Editor.
Most tabs have the same name as their case level counterpart. For example, the settings for the Prices tab of the Case Editor can be found on the Prices tab of the Global Editor.
Here are a few exceptions:
Scenarios are not dynamic links. If the user changes something in the scenario, they will have to repeat this process to update the cases.
Apply Scenario only replaces or adds data, it never erases it. If your case has a Fixed Cost and you apply a scenario with no Fixed Cost model, the Fixed Cost already on the case is not deleted.
If you change a model within a scenario, that is linked. So once you save the change in the models file, it will change throughout the database.
If a group only contains a single case, the summary level is often suppressed because it’s the same value as the single case. This can cause problems when running Summary Only reports as these grayed out levels will not report. To fix this:
You can right click a Data Field that is already in your Filter to create an indented/nested logic statement. This allows you to check multiple values for a single Data Field.
For example: You want to Filter for all the Proved cases in either Texas or Louisiana.
By right clicking to create the nested logic statement, you can check for multiple Values on a single Data Field. If you need to check for more than two values, repeat step 4 to create as many additional nested logic statements as needed.
A Summary Plot case is only designed to gather production volumes, it does not allow for any economic inputs like prices or expenses. Instead, try creating a Unit case. It gathers volumes just like a Summary Plot, but has the added ability to allow economic inputs.
It’s worth mentioning that a group case is not meant to be the same as summing the economics for all the cases in the group. If you want to view the combined economics, try running a report on a group of cases and looking at the Grand Total summary page of your report.
If you have the “UNRESOLVED” watermark on your graphs, then your graphs might be incorrect. The economics have not been run with your recent changes included. To update the economics with all of your recent changes and to remove the Unresolved watermark, run any of the Economics reports on all of the cases. This will force the economics to run with all of the current settings, and all of the graphs will be updated with a correct representation of the economics.
For a Single Case:
For multiple cases:
The Excel Spreadsheet reports are driven by Access queries. If you do not have MS Access installed, the query cannot run and will cause the program to terminate abruptly. You would need to install MS Access and then you should be able to run the Excel Spreadsheet reports.
The Excel Spreadsheet reports are driven by Access queries. It attempts an automated export from Access to Excel to view the report output, but this can fail for various reasons. If the report doesn’t open in Excel directly, the best option is to open the Access file and run the Query manually.
You can find the PHDWinOut.mdb file in the Reports folder of the PHDWin installation directory. Just open the file and look for the Query that matches your Excel Spreadsheet report. In PHDWin you can double click the Excel Spreadsheet report in the Reports and Views list to view the name of it’s associated Access query. You can double click the Query in Access to run it and view the data from your report.