I.    File Menu

A.    Database Operations

1.    Switch Database

If your company has a requirement for more than one database, you may use the Switch Database utility to connect to a different database.  You may browse anywhere on your network or computer to locate a different Logger's Edge database.

Generally, your database files will be stored under the default directory: "C:\Program Files\Caribou Software\Logger's Edge\ Database".  Database files are stored with the extension "*.mdb" which is the default extension for Microsoft Access database files. (Your computer may be set to hide the "mdb" extension, so don't be confused if you do not see such extensions on your computer.)

Warning:  You should not attempt to switch to a database file named HarvestBoss0_*.mdb.  This database should be a hidden file with a read-only attribute.  It is the template database from which all NEW databases are created.

2.    Compact Database

The compact database utility reduces the file size of the database to which you are currently attached. The utility will remove any “empty” space within the database and improve the performance of the program. We recommend that you compact your database at least once a month, and as frequently as once every week for larger organizations. 

The Compact feature requires that you have Microsoft Access 2000 (or higher) installed.

3.    Backup/Compact Database

A schedule should be set up to perform regular maintenance on your Logger's Edge database. A backup should be created regularly and stored off-site.  

The backup/compact utility can be used to create a backup copy of the database that is compacted. This is an easy way to create a file that can be stored off-site.  This utility creates a compacted copy of the database to which you are currently connected.

The backup function will use an auto-naming convention that indicates the date / time as the file name and appends the extension ".mdb".  You can override this auto-naming feature with your own file naming convention, but it is generally useful to indicate the vintage of the backup file so that older backups can be periodically purged.

Be sure to note the subdirectory in which you are creating the backup of your database.  The default location is "C:\Program Files\Caribou Software\LoggersEdge\Database", but you can change the location to which the file will be written using the drop-down "Save in" box at the top of the window.

The Backup/Compact feature requires that you have Microsoft Access 2000 (or higher) installed.

Once you backup the files, you should burn the backup file to a CD or DVD. With Windows XP, this functionality is built in. Here is a link the the Microsoft website for burning a CD or DVD using Windows XP.

Burning a CD or DVD using Windows XP

4.    Backup Only

For users that do not have Microsoft Access, the "backup only" utility can be used to create a straight (not compacted) backup copy of the database. This is an easy way to create a file that can be stored off-site. The backup database utility creates a copy of the database to which you are currently connected.  This utility does not compact the database.

The backup function will use an auto-naming convention that indicates uses the date / time as the file name and appends the extension ".mdb".  You can override this auto-naming feature with your own file naming convention, but it is generally useful to indicate the vintage of the backup file so that older backups can be periodically purged. 

Be sure to note the subdirectory in which you are creating the backup of your database.  The default location is "C:\Program Files\Caribou Software\LoggersEdge\Database", but you can change the location to which the file will be written using the drop-down "Save in" box at the top of the window.

Once you backup the files, you should burn the backup file to a CD or DVD. With Windows XP, this functionality is built in. Here is a link the the Microsoft website for burning a CD or DVD using Windows XP.

Burning a CD or DVD using Windows XP

5.    Create Empty Database

In the event that a fresh new database must be created, use the Create Empty Database utility to build a new blank database. The blank database contains all of the required tables and default records The Logger's Edge uses.

The Logger's Edge uses a database file named HarvestBoss0_*.mdb as a kernel database to create a new database.  The program first makes a copy of the kernel database and then renames it using the name you provide.  The HarvestBoss0_*.mdb database should be a hidden file with a read-only attribute.  You should not delete it nor move it to a different directory.

Note:  if you want to create a new database containing all your configuration settings, but purged of existing load ticket, time ticket data, etc., do not use this feature.  This feature will start with a database with a standard configuration, which will not reflect any special configuration changes done for your account. Instead, use the File | create Primed Database menu item.

6.    Create Primed Database

In the event that you want to create a new database that contains all your basic setup data, but has all your activity and pay data (time slips, load slips, statement detail records) cleaned out, use the Create Primed Database utility to build a new primed database. The primed database retains all of your setup data, such as employees, trucks and equipment, but clears out all time and load slip data.  The primed database is useful to send to users that are entering data remotely or for creating a new database at the start of the log year.

The primed database is created from the database to which you are currently connected.  The Logger's Edge first makes a copy of the current database and renames it using the name you have selected.  Next, The Logger's Edge cleans out the tables that contain the transactional data you do not wish to retain, such as time slips, load tickets or statement payment records.

The set of data tables that are cleaned out is set up in The Logger's Edge system tables.

The following is a list of Tables that are cleaned out by default.  Talk to a Caribou support representative if you would like to change the tables that are cleaned out.

TABLE NAME
Advances
Block Cost Details
Employee Expenses
Employee Statements
Employee Statement Details
Equipment Time
Holdbacks
Hourly Pay Details
Invoice Details
Invoice Revenue Contracts
Invoices
Load Slip Activities
Load Slips
Load Truck Cost
Load Slip Revenue
Miscellaneous Expenses
Miscellaneous Income
Production Details
Production Details Contractors
Time Detail
Time Details Contractors
Time Slip Header
Vendor Statement Details
Vendor Statements

7.    Clear Users

The Logger's Edge records each user in the database when they open the program and clears the user when the program is closed.  The "active user" records are used to prevent the pay calculators from being run if other users are in the system.  In the event, however, that a user abnormally leaves the system (e.g. just turns off their computer with the power switch while the program is running), the user is not cleared out of the system and will prevent the pay calculators from being run.  This "Clear Users" utility function is designed to clear out any residual user records in order to allow the calculators to be run.  This function should only be used if you are 100% sure there are no other legitimate users using the program.

 

B.    Configure Statements and Invoices

The standard vendor, employee and invoice statements that are included in The Logger's Edge can be configured to some extent to meet your business needs.  In addition, you can have statements that are in one format for some vendors, but are in a different format for others.  For example, you might want to use one type of format for trucking contractors, but use another format for harvesting contractors.  You can also have different formats for your employee statements, vendor statements and invoices.

1.    Configure Employee Statements

The statements that are prepared by The Logger's Edge can be configured to meet your business needs.  The configuration functionality only applies to statements where pay is based on loads.

For each of the three basic types of statements: (1) Employees, (2) Vendors, and (3) Invoices, you can select the data items that will appear, the order in which they will appear, and any sub-totals.

For each basic type of statement, you can have multiple formats.  For example, within your vendor statement category, you may want to have a statement format for your truckers, one for your landowners, and one for everyone else.

As explained in more detail below, you determine which statement format applies to which employee, vendor, or customer when you first set up an employee, vendor, or customer. There is a column in the far right of the employee, vendor, and customer lists where you indicate the statement format to use for that vendor.

In the selection window that appears when you select one of the three menu items, you can either select an existing statement format or create a new statement format.  You create a new format by typing a format name that does not already exist in the list.

In the window, there is one statement format (Standard Employee) that comes installed with The Logger's Edge.  If you want to create another variation, just key in a new name (like 'Employee Format 2' in the above window) and click OK.

Once you select a format, you are presented with an edit grid.  (The same type of grid will appear for all statement types -- Employees, Vendors, and Invoices.)

The columns are defined as:

Again, the formatting only applies to pay based on loadslips.

An example of a formatted vendor statement that appears from the above selections is shown here.  Employee statements will look similar to this example.

In order to apply a specific format to an employee, navigate to Setup | Workers | Worker Setup.  In the 'Statement Type Code' column, you can select the statement format that you want to applied to each employee.

Thus, you can have different formats for different employees.

2.    Configure Vendor Statements

The statements that are prepared by The Logger's Edge can be configured to meet your business needs.  The configuration functionality only applies to statements where pay is based on loads.

For each of the three basic types of statements: (1) Employees, (2) Vendors, and (3) Invoices, you can select the data items that will appear, the order in which they will appear and any sub-totals.

For each basic type of statements, you can have multiple formats.  For example, within your vendor statement type, you may want to have a statement format for your truckers, one for your landowners, and one for everyone else.

As explained in more detail below, you determine which statement format applies to which employee, vendor, or customer when you first set up an employee, vendor, or customer.

In the selection window that appears when you select one of the three menu items, you can either select an existing statement format or create a new statement format.  You create a new format by typing a format name that does not already exist in the list.

In the window, there is one statement format (Standard Vendor) that comes installed with The Logger's Edge.  If you want to create another variation, just key in a new name (like 'Truckers' in the above window) and click OK.

Once you select a format, you are presented with an edit grid.  (The same type of grid will appear for to all statement types  -- Employees, Vendors, and Invoices.)

The columns are defined as:

An example of the formatted vendor statement that appears from the above selections is shown here.

In order to apply a specific format to an vendor, navigate to Setup | Vendors.  In the 'Statement Type Code' column you can select the statement format that you want applied to each vendor.

Thus, you can have different formats for different vendors or categories of vendor.

3.    Configure Invoices

The invoice statements that are prepared by The Logger's Edge can be configured to meet your business needs.  The configuration functionality only applies to invoices where pay is based on loads.

For each of the three basic types of statements: (1) Employees, (2) Vendors, and (3) Invoices, you can select the data items that will appear, the order in which they will appear, and any sub-totals.

For each basic type of statement, you can have multiple formats.  For example, within your vendor statement type, you may want to have a statement format for your truckers, one for your landowners, and one for everyone else.

As explained in more detail below, you determine which statement format applies to which employee, vendor, or customer when you first set up an employee, vendor, or customer.

In the selection window that appears when you select one of the three menu items, you can either select an existing statement format or create a new statement format.  You create a new format by typing a format name that does not already exist in the list.

In the window, there is one invoice format (Standard Invoice) that comes installed with The Logger's Edge.  If you want to create another variation, just key in a new name (like 'Weyerhaeuser Invoice' in the above window) and click OK.

Once you select a format, you are presented with an edit grid.  (The same type of grid will appear for all statement types -- Employees, Vendors, and Invoices.)

The columns are defined as:

An example of the formatted vendor statement that appears from the above selections is shown here.  Customer invoice statements will look similar to this example.

In order to apply a specific format to a customer, navigate to Setup | Customer.  In the 'Invoice Type Code' column you, can select the statement format that you want to applied to each customer.  In the example, the 'Weyerhaeuser Invoice' format has been selected for Weyerhaeuser.

Thus, you can have different formats for different customers.

 

C.    Setup File Exchange

The The Logger's Edge includes the ability to import load data from external files.  For example, if you receive a load listing from the mill(s) to which you deliver, you can import those loads into The Logger's Edge without having to rekey the data.  As you can imagine, if you handle hundreds of loads a week, this capability can be a real time saver.  In order to import the loads, you first need to configure the import format.  This configuration maps the input load data into the appropriate data items for the The Logger's Edge.  There are actually three import formats that can be used: (1) Loads, (2) Load Revenue, (3) Load Activities.  There is also a fourth menu item (Import File Translations) where you can set up translation rules for imports.  For example, if an import file uses the term 'LP' for lodgepole pine, whereas you use the term LP_PINE in The Logger's Edge the 'Import File Translations' function allows you to convert LP into LP_PINE when you perform an import.

 

1.   Configure Load Import

The Logger's Edge allows you to define an import format so that you can take standard files (e.g., Excel files or tab delimited files) that a mill sends you and import them into The Logger's Edge.  If you deliver to multiple mills, you will likely need to define a format for each mill, since each mill is likely to provide you with the load data in different formats.

Assuming any given mill provides you with load data in the same file format consistently, you will only need to define the import format for that mill once.  Thereafter, you will be able to import the loads through a one-step process, assuming you have all your load information (e.g., trucks, blocks, etc) already set up in The Logger's Edge.

For details on this feature see How To Configure A Load Import

2.   Configure Load Revenue Import

The Logger's Edge allows you to define an import format so that you can take standard settlement files (e.g., Excel files or tab delimited files) that a mill sends you and import the revenue values (as opposed the basic load attribute data) into The Logger's Edge.  If you deliver to multiple mills, you will likely need to define a revenue format for each mill, since each mill is likely to provide you with the load revenue data in different formats.

Assuming any given mill provides you with load revenue data in the same file format consistently, you will only need to define the import format for that mill once.  Thereafter, you will be able to import the load revenue through a one-step process. 

For details on this feature see How To Configure A Load Revenue Import

3.    Load Activities

The Logger's Edge allows you to define an import format so that you import the activities, equipment and workers related to your loads into the system.  For example, for each load, you might have a feller, loader and skidder that you want to track and/or pay for working on the load.  You can work with your data in an Excel workbook, save as a tab delimited file, and then import it into The Logger's Edge.

For details on this feature see How To Configure A Load Activity Import

4.    Import File Translations

This function allows you to map import file values to the values you use in your database.  Thus, an import files does not have to use terms for data items that are the same as yours, but can be those use by each specific mill. 

For example, if a mill uses '42', whereas you use 'LP' for Lodgepole Pine, you can set up a mapping entry that will translate an entry of '42' in the import file into 'LP'.  (See the fifth row in the grid below.)   And, because The Logger's Edge supports multiple imports, you could set up another mapping entry of 'LPOLE' into 'LP' for another mill's import.  For example, Canfor might use '42' for Lodgepole Pine, whereas West Fraser might use 'LPOLE'.

In the grid, the columns are:

For example, line 4 in the grid above can be interpreted as follows:  For import configuration 100 (Canfor), for the field C_PART_4_CODE (Species), if the import file has the value of '33', convert the value to 'FIR' on import.