1. How do I set up FPS with Windows 7 and Access 2007?


2. What is new in Version 6.60?
   
   
3. I have recently installed FPS. Why do I get the following message when attempting to run certain utilities?
   
   
   
4. I have upgraded to version 6.60 but now my FPS utilities (Cruise Compiler, Growth Model, Harvest Scheduler...) will not run correctly.
   
   
5. Why am I seeing #ERROR when I run reports from the FPS drop down menu?
   
   
6. When I try to run a FPS utility from the drop down menu, an error message appears stating that FPS cannot find the function.
   
   
   
7. How do I go about running a harvest depletion and year end inventory update? ( Downloadable PDF)
   
   
8. In my DIBCLS table I am getting unexpected results in the GRADE column.
   
   
9. When I run a report I get an error stating that FPS cannot find a file called fbri.jpg.
   
   
10. I get an OVERFLOW message when running FPS utilities, then the utility stops running.
    
    
11. How do I import data from a mobile device?
    
    
12. What are the DAMAGE codes that FPS uses in the PLOTS table?


13. How do I set up FPS with Windows 7 and Access 2007?

Question 1: What is new in Version 6.60?

• Expansion of the number of growth projection periods to 100 periods (recommend 20);
• There are now commercial thinning treatment thresholds which trigger only if cut volume exceeds your pre-specified limit;
• Thinning priorities may specify up to three preferred tree species after thinning;
• You may invoke fill-planting additional tree stock by species at any period;
• Log values may now be specified based on board, cubic, weight or cord yields per acre;
• Log sorts may include/exclude SORTS table dimensions, defect, log position and values differentially by species;
• The Harvest Scheduler now provides volume removal distributions by species and sort;
• A new Selection Verify Tables menu checks all database tables for correct status prior to year-end reporting and harvest planning;
• A new Editors menu verifies Physical Site values for under-estimated site levels;
• Green and dry weight is now reported by Dbh and Lob Dib class for total stem, merchantable bole, bark, branch and foliage. This includes carbon sequestration for total biomass and harvest volumes;
• We have developed a new Physical Site Capacity methodology which separates growth capacity due to silviculture, site index, genetics and bio/geo/climatic zone;
• First approximation Regional Species Libraries are being prepared for all regions across North America based on the new FBRI site productivity stratification methodology; and,
• The FPS database is being re-structured to facilitate upgrading to Windows Vista format and startup time due to Microsoft virus checking of imbedding visual basic code.

> BACK TO TOP

Question 2: I have recently installed FPS. Why do I get the following message when attempting to run certain utilities?
It is possible that something went wrong with the product registration during the install.

• Using windows explorer, navigate to the FPS install directory (often C:\FPS\).
• Double click FPSPost.exe in your install directory and fill out the form. Click on "Post" when the form is filled out, then click "Close".

> BACK TO TOP

Question 3: I have upgraded to version 6.60 but now my FPS utilities (Cruise Compiler, Growth Model, Harvest Scheduler...) will not run correctly.
There are several possible causes of this problem. We have listed the most common causes with their solutions here in this section. Try these fixes one at a time until the problem is resolved. If the problem persists, please contact FBRI for assistance.

1. Run the database integrity checker. It is possible that the utility being used is attempting to write data to columns or tables that only exist in newer versions of the database (for example the green and dry weight calculations that were added into version 6.60).
   • Open the database and click "Start" on the FPS startup screen.
   • Select under the menu Database--> Check Database Integrity. If nothing happens, leave the database open. Use windows explorer to navigate to the FPS install directory. Double click the executable named "FpsTbls.exe".
   • Click the Start button. Once the utility checks your database it will add the missing tables and columns.
   • Press Enter to continue.
     
     
2. It is possible that something went wrong with the product registration during the install. This can be fixed by first locating the install CD ROM containing the latest version on FPS.
   • Use windows explorer to navigate to the FPS install directory.
   • Locate a file named "FPSDate.dll". Delete this file, it may be corrupt or out of date. We are going to re-create it.
   • Insert the FPS install CD into the CD ROM drive and cancel out of the auto-install menu. In windows explorer navigate to the CD ROM drive and right click on it. Select "Open". On the CD navigate to the \FPS directory and locate a file named "FPSPost.exe". Copy FPSPost.exe and past it into your FPS install directory on your PC.
   • Double click FPSPost.exe in your install directory and fill out the form. Click on "Post" when the form is filled out, then click "Close".

> BACK TO TOP


Question 4: Why am I seeing #ERROR when I run reports from the FPS drop down menu?
The problem may be that the Habitat Classification has not been run for the stands that are flagged. Prior to running this utility not all stands have species, size, density, age, site, precipitation, elevation and solar radiation stratification values necessary to create all Year-end reports across all stands in the inventory. Select under the menu Strata---> Create new Habitat Classification.
> BACK TO TOP

Question 5: When I try to run a FPS utility from the drop down menu, an error message appears stating that FPS cannot find the function.
The problem is that the macro security is set too high. When higher security levels are set, Microsoft Access will block certain functions that can be exploited by hackers, hoodlums, criminals, biometricians, and other unsavory sorts. While lowering the security level may open up vulnerabilities in Access and/or Windows, we must allow some things to run in order to get the job done. After all, turning off the power will make the PC absolutely secure! Read more here.

• In the database select the menu Tools-->Macro-->Security.
• Click on the radio button for "LOW" and click OK.

In some versions of MS Access the security level can not be changed through a drop down menu. There will not be a menu item called Security under the Macro menu. The system's registry will need to be changed manually to disable the "sandbox mode" which blocks macros. Please refer to document 239482 in the Microsoft knowledge base for more information.
> BACK TO TOP

Question 7: In my DIBCLS table I am getting unexpected results in the GRADE column.
The FPS software allows you to merchandise your forest by dynamically specifying the parameters of log dimensions, defect, log position and values differentially by species. Up to three sorts per species can be defined in the SPECIES table. For many land owners three sorts are enough to characterize the forest, but if additional sorts are needed the SORTS table is available. FPS will find the best SORT for each log it moves through the SORTS table. If a log matches the criteria of more than one sort, FPS will assign that log to the sort with the highest value. In order to understand how FPS assigns sorts we must determine what version of FPS is currently installed.

• Version 6.60 and later: FPS assumes that the three sorts in the SPECIES table are enough unless it is specifically told to go out to the SORTS table. The user may notice that only #1, #2, and #3 show up in the GRADE column of the DIBCLS table. These are the sort/grade codes for the three sorts that can be defined in the SPECIES table. Let us assume that the user has set up the SORTS table for seven Douglas Fir products wants all volume to be distributed into these seven sorts. In the SPECIES table there is a column named SRT1_BAS. This column allows the user to define the basis for valuing the sort. The user can enter "9" in the SRT1_BAS column to force FPS into the sorts table. FPS can be asked to jump out to the sorts table at any of the three Srtx_BAS columns.
• Versions earlier than 6.60: Basically, FPS goes out to the SORTS table any time it is not able to merchandise a log with the three sorts in the SPECIES table. Sometimes an unusual piece (that one big old growth Sugar Pine that got picked up on the last cruise) will unexpectedly be categorized according to the SORTS table because the SPECIES did not include a definition broad enough to include it.

> BACK TO TOP

Question 8: When I run a report I get an error stating that FPS cannot find a file called fbri.jpg.
In some versions of the database FPS links to a jpeg image in order to include it on the top left hand corner of the report. If the user does not have this image in the default install directory for FPS, the report will fail to be generated. Download the picture here and put it in a directory called C:\FPS. This should solve the problem. In newer database versions the logo is stored in a Form called Logo.
> BACK TO TOP


Question 9: I get an OVERFLOW message when running FPS utilities, then the utility stops running.
This is a troublesome error and often a difficult one to figure out. Someplace in the computations being run by FPS a number is being divided by zero. This results in an error that shuts down whatever utility was running. Someplace in the database is a null field or a zero field that should have a number greater than zero. This is almost certainly unique to the individual user's dataset. Try to observe what stand number was last processed by the utility in order to get clues on where to look. Good luck gumshoe!
> BACK TO TOP


Question 10: How do I import data from a mobile device?
Download a .pdf file containing procedures here. Also, download a zip file containing helpful update queries here.
> BACK TO TOP


Question 11: What are the DAMAGE codes that FPS uses in the PLOTS table?
FPS provides the cruiser with a set of damage codes for use in the DAMAGE column of the PLOTS table. The codes are always three digit (unless 0 is used). A lookup table is available for download here.
> BACK TO TOP