Change History for Royalty Management Program

 

 


Version 5/5/08

 

  1. Modified the Payment window, decimal interest selection to update the Interest Type automatically when an alternate decimal interest is chosen. (From a user request).

 

  1. Changed the Property index State to include the County as a secondary sort. (From a user request).

 

  1. Increased the number of decimal places for the Property - Net Acreage column (Legal.dbf) and Lease – Net Acres column (Lease.dbf) from 2 to 6 decimal places. (From a user request).

 

  1. Increased the size of the Lease Number column in Division Orders and Payments from 12 to 20 characters (Payor.dbf & Payments.dbf).  Also in all related tables (Expenses.dbf & Prop_Exp.dbf). (From a user request).

 

  1. Added a new “Summary Royalty Report by Payor W/H” which is the same as the Summary Royalty Report by Payor except that the additions and withholdings are separated. (From a user request).

 

  1. Added a new “Payor Summary Report” which is the same as the Summary Royalty Report by Payor W/H except that the data is not grouped by Lease Number.  (From a user request).

 

 

 

Version 2/2/07

 

  1. Modified the “Schedule of Royalty Income Report” (Total Income Report) to use the selected date value (Check or Deposit Date) on the Report Criteria screen when grouping the data (from a user request).  The report previously used only the Check Date for grouping data.

 

  1. Added a new report “Schedule of Royalty Well Income” by copying the existing Total Income Report and using the Well Name to group the data.

 

  1. Modified the Edit Report adding totals for the Total Quantity column.



 

Version 10/16/06

 

  1. Added Well Name and Property name to the “Detailed Royalty Report by Product”, “Summary Royalty Report by Payor”, “Monthly Revenue Report by Product”, and “Missing Payment Report” (from a user request).

 

  1. Printer Setup issues …

 

 

Version 03/22/06

 

  1. Corrected a printing problem from the Table View print option.

 

 

Version 08/23/05

 

  1. Modified the program settings to prevent file / record locking errors when used on a network by multiple users.  User may need to modify the BDE configuration “Local Share” parameter to True.

 

 

Version 05/23/05

 

  1. Added State to the Property Transactions report criteria selection.

 

 

Version 04/14/05

 

  1. Changed the Global Change screen to stay open after each change.  The user will now click the Cancel button to close the screen.

 

  1. Added a default Deposit Date to the Oildex Data Import screen.  The user can enter a deposit date that will be used for all transactions that are imported or leave it blank and the check date will be used (as it worked previously).

 

 

 

Version 03/21/05

 

  1. Fixed a problem with the format of Contact phone numbers as reported by a user (Company phone numbers were okay).

 

 

Version 02/09/05

 

  1. Added the Property Transaction Type table to the installation (it was missing from the previous installation file).  Also added the Query Data table to the installation since some older users will need the updated version.

 

  1. Fixed a problem with adding records to the Property Transaction screen (error reported by user).

 

 

Version 01/20/05

 

  1. Changed the Oildex Data Import, how the check date is determined.  If the Transmittal Date was in the current year and the Effective Date was in the previous year, the check date would be in the current year which is incorrect.

 

 

Version 12/29/04

 

  1. Fixed Contacts, file was missing in 12/20/04 version.

 

 

Version 12/20/04

 

  1. Added new report “Property Transactions by Category” as per user request.
  2. Added a print button to the Table View screen and a record / column selection screen behind it.  Only so many columns will fit on the paper.

 

 

Version 11/26/04

 

  1. Modified the Oildex Import Data screen, if the number of records was larger than 240 (or so) the size calculations on the file were incorrect.  Changed how the import file size was calculated to correct the problem.  (Did not occur on smaller files.)  Changed the View Raw Data button to be an Import Preview (test) button.

 

 

Version 08/16/04

 

  1. Added API Number entry field on the Division Order screen.
  2. Added API Number to the Division Order Property Report.

 

 

Version 05/19/04

 

  1. Modified the Oildex Import to fix two reported errors.

 

 

Version 04/23/04

 

  1. Revised the Property Expense option to be a Property Transactions screen that can handle both expenses and revenue.  Added a Transaction Type column to hold Expense or Revenue and changed the EXP_TYPE column to TRANS_CAT for categories.  Revised the Property Expenses report to be the Property Transactions Report.

 

 

Version 04/05/04

 

  1. Added a Property Expense option to the Property screen.  The Property Expense selection will be used for expenses such as Ad Valorem Taxes that are paid by the property owner.  There is a Property Expense Categories table that the user can add additional expense categories, as they require.  This table is maintained from the Table menu selection.
  2. Added a user column to the Data Query code to separate users on a network installation.

 

 

Version 02/13/04

 

  1. Modified the Import Data section, fixed an error “Other Additions and Other Deduction values were not being adjusted for the decimal place”.
  2. Added Royalty Owner volumes to the Production by State report (03/23/04).

 

 

Version 06/05/03

 

  1. Added to the Import Data help and added a button to view the CDEX data once it has been imported.  Made sure the update files for the Division Orders and Payments increase the Owner Number to 14 characters to match the CDEX Lease Number.

 

 

Version 05/13/03

 

  1. The file format for Oildex imports apparently is not 100% standard.  Files received from John Jernigan had a line feed character at the end, but no carriage return (CHR(10) but no CHR(13), typical ASCII text files have CHR(13)CHR(10) at the end of a line).  Previous Oildex samples included the required characters.  Oildex Support responded that each Payor creates the files and they just send the files to the correct person.  Changed the Oildex import to import the data into a memo field and then create a standard ASCII file of our own to import.

 

  1. On the Import Data screen, if the user selects data from a different drive than the C drive, the file name is not picked up properly by the program code.  Since Visual dBASE only recognizes the 8 character file names (short name), the short name is being read from the file attributes.  Normally, attribute 6 is the short file name, however if the Oildex file is on drive R (for example), the short file name is missing on files with a name of 8 characters or less.  Changed the code to allow for this and select the correct file name.  This error was reported by user John Jernigan.

 

  1. Also changed the Import Data screen by adding a button to view the raw data after it has been imported.  Used the last column in the CDEX_1 table to indicate which records have been imported.  Added instruction note to not use long folder names (could not work around this problem found in Win NT or higher).

 

 

Version 04/15/03

 

  1. The “Leased Acreage Report” had errors in the set up program.  The report file and report program variables were not being passed to the report filter.  Other reports were changed, but this one was missed in the previous update.  This error was detected and reported by Teresa Parker of FNB&T Okmulgee.

 

  1. The “Property Lease Report” created an error on line 452, “Maximum number of locked records exceeded”.  Added code to unlock each record after it was updated.

 

  1. On “Leased Acreage Report”, properties with multiple leases may have been skipped on the report if the first lease was not active (date released not blank).  Modified the Repdata program to include all lease records and a criteria for RDATE to be blank.  The RDATE criteria was in the report selection criteria inside the rpt file and would filter out records there.  Now only qualified records are submitted to the report.  This error was detected and reported by Teresa Parker of FNB&T Okmulgee.

 

 

 

Version 03/27/03

 

  1. Changed the “Select Account” to update the new account location properly.  This error only affected users who had their program install somewhere other than the C:\RMP folder.  A variable in the program code was initialized to C:\RMP and never reset when the account was changed.  This error was first reported by Trinity University and then again by John Jernigan.

 

 

 

 

 

(began after Version 12/11/02)