Job Boss

User Defined Reporting Troubleshooting Guide

Common Errors associated with Access

A Valid File is missing from the Specified Location

This error is caused by one of two reasons, either there is no jbudrpt.mdb in the Custom Report Path directory, or the Custom report path is not configured.

Verify the custom report path.

In the JobBOSS program, go to View and User Options

Verify the existence of the Jbudrpt.mdb in the program directory

If a Jbudrpt.mdb does not exist in this location, we provide a blank jbudrpt.mdb in the Client70\BlankDB directory. You can copy it into the Custom Report Path directory from there. If you have user defined reports that function correctly on another workstation, you can copy them from that workstation to the affected machine.

Grey screen when running an Access User Defined report.

This phenomenon occurs when a User Defined report on the menu has no actual report in the Jbudrpt.

To verify the report, open the Jbudrpt.

The Microsoft Jet Database engine cannot find the input table or query

‘ ’. Make sure it exists and that its name is spelled correctly.

Attempts to run an access report result in the error message below. The name of the input table or query can vary, but it is usually part of the report you are trying to run.

The issue is that the linked tables in the jbud are missing and so the database is no longer in communication with the Jobboss.mdb, your main data source. This usually happens following a windows update, and has been traced directly to an issue with the Msjet40.dll, service pack 7.

To validate the issue, open the Jbudrpt.

Required Registry information missing from the Registry:

Users may see the following error after Launching Jbudrpt or trying to run a user defined report.

"Required registry information is missing and this application cannot run. Please rerun setup to correct problem."

This error can be caused by multiple things:

1) The JobBOSS User Options is pointing in the incorrect location

2) The jbudrpt that the reports live in no longer live where the User Options are pointing to

3) There may be a conflict in Microsoft Access

To decide which avenue to follow, try this simple test.

On the Reports tab, push the button labeled User-Defined. You should get a form similar to the illustration below. Push the Launch Jbudrpt button. Do you get the error message “A valid file was not found at the specified location” ?

If yes, see "A Valid File is missing from the Specified Location"

After positioning a Jbudrpt file in the correct location, try your report again.

Do you continue to receive the error message “Required information missing from the registry..”?

1) Verify that the Custom Reporting path in the User Options is pointing in the correct location

In JobBOSS, in the upper left hand corner where the menu bar options are for File, Edit, View, etc... Click on View

Select User Options

Click on the Printer Options tab

At the bottom there is a Custom Reporting Path, this must be the path where the jbudrpt lives

2) Verify that the jbudrpt does actually live where the Custom Reporting Path is pointing to.

Users can use Windows explorer to browse to this location

If the file does not live in this location users can copy it from a working computer

3) There may be a conflict with Microsoft Access

This indicates a possible conflict with Microsoft Access, that may have occurred if the Access Runtime and the Full Version of Microsoft Access reside on the same computer, or it may result from a corrupted installation of either one. In any case there are several resolutions for this problem, depending on the severity of the conflict on the local machine. It is always a problem with the local workstation, not a network issue.

Resolution One:

Determine which version of Access the machine has.

After the Repair is complete, I would advocate rebooting the Computer even if the program does not require it.

If the error message persists, we then move onto the next resolution.

Resolution Two

Remove Runtime and Repair the Full Version

Now it is necessary to go to the registry and redirect all references to MS Access.

Go to Start, then Run. In the run line, type regedit.

Push the plus in front of H-Key Local Machine

Now that the registry values are in place, we will need to repair the Office installation. With the original installation disc in the CD ROM, go back to the

Control Panel

Add/Remove Programs

Microsoft Office 2000 Professional.

Cannot find “C:\program files\Jobboss\jbudrpt.mdb

This error is a result of an incomplete or corrupted install of Microsoft Office. Use the same troubleshooting method recommended for the Required Information Missing from the Registry error

You used a method of docmd object to carry out an action in visual basic but then clicked cancel in the dialog box

Typically this is an issue with a local copy of jbudrpt.mdb. If other workstations are able to successfully launch the report(s) in question, copy the jbudrpt.mdb from a working workstation to the one that receives this error.

Using Crystal to create User Defined Reports

If you intend to use the Custom Report to replace a JobBOSS Standard report, you will want to MODIFY a Standard report. If you wish to customize a JobBOSS report to use, without removing the Standard report, you will wish to COPY the standard report.

Modifying JobBOSS Standard Reports Using Crystal

(requires JobBOSS 7.2 or greater)

Copying Standard reports and using them in the JobBOSS Menu

Adding fields and calculations to the Modified Report

If you use Crystal to make more than cosmetic changes to the rpt file, you may add fields to the report. There are two common methods of accomplishing this, either modifying the htm query statements or for the less skilled programmers it is possible to add fields to the report that using a direct database connection. Both methods will be detailed in the next section.

Adding a field to the report using a direct link to the JobBOSS.mdb

Depending on the complexity of the report, it may be possible to simply add fields from the JobBOSS database to the report. To do this we must add the JobBOSS database source Jobboss32 to the report.

Open your crystal report. From menu above select database/Database expert.

You will be presented with a dialog box. Select Create New Connection.

Choose ODBC (RDO)

You will be presented with a Data Source Connection dialog box. Choose Jobboss32.

Another dialog box will enable you to enter the Security information needed to access the db

User name is ALWAYS support and password is ALWAYS lonestar. This is case sensitive, lower case only.

Now that you have access to the database, you will need to specify the table that contains the data you are looking for.

Choose the table from the left and then click the arrow button to move it to the selected box.

You now need to choose the TTX file that the report is currently using as a data source. Press the little button with the three dots (…) to open a search box. Your file is ALWAYS in the Client70\Reporting\User-defined folder

Now that you have the two data sources specified, you need to link them on a common field. In the example above, I have linked the SDescription field from the TTX document to the Description field of the Material table.

You will receive this warning as a matter of course. Say OK.

Now that you have your data sources defined and linked, you need to add the field to the report. On the left menu, choose the Database Fields, and hit the plus in front of the table.

It will expand to give you a list of fields. In this example I wanted the Material name. Select the field on the left and move to the DETAIL section on the right.

You are now able to format the text in the field; right mouse click and choose format text

Change font type and or size.

Save the report and close Crystal.

Your report is now ready for use in JobBOSS, with the additional field.

Modifying the HTM query statements

Our reports are comprised of htm files that gather data, ttx files that map out available fields, and the rpt files that display that data.

Use Notepad to open the htm file in the client70\user-defined directory, locate the query statement that you desire, and modify the statement.

After you have modified the htm select statement for the new fields, you need to update the ttx to include those new fields. You can use Notepad to open the ttx file for modification. Once you have updated the ttx file for the map, you will need to tell the report where to look for that new ttx information

You must reimport the TTX file to be able to choose the newly defined fields open the report file you were working with. The User Defined report copied the report files to the Reporting\User Defined folder. The report is still pointing to the TTX file in the Reporting folder. Use Database - Verify Database to change which TTX file location is being used.

Creating reports in Crystal for use with JobBOSS.

Saving the report for use in JobBOSS.

Adding a User Defined Report to the Jobboss Reporting Menu

You see your User Defined report on your JobBOSS Report Menu

Common Errors associated with

Crystal User Defined Reports

Script or Runtime Error- File not found

Line: 33

Char: 28

Error: File not found

Code: 0

URL: file://F:\Client70\Reporting\User-Defined\UD_Report.htm

Sometimes this error will display as a Runtime Error.

Runtime Error

File Not Found

This error results when you are attempting to run a Crystal Report that does not reside in the \\..Client70\Reporting\User-Defined Directory. Check the location of the report and if it is not located in the proper directory, move it to the proper location.

If the report actually exists in this directory, count the number of characters in the name of the report, including spaces and underscores. The jbidx2k, where the menu link is stored to use the report in JobBOSS, is limited to 30 characters. If a report name exceeds this length, only 30 characters will be written.

Script Error – Invalid Directory

Line: 92

Char: 29

Error: Invalid Directory

URL: file://F:\Client70\Reporting\User-Defined\UD_report.htm

Once the crystal report is saved to the proper directory, and the JobBOSS Report Menu item has been created, attempts to launch the report from within JobBOSS are met with script error above. If you are running 7.2 or 7.3, the probably lies with the UD_report.htm, it may be faulty.

Resolution: Download the correct htm file from the JBHELPS website, Support Hotfixes www.jbhelps.com

Support\Downloads\7.x\7.x Hotfixes\UserDefinedLaunchPageHotfix.exe

Parameter value missing from the report

Running a User Defined report in which a Parameter Value has been used, but it does not appear when you try to run the report from within the JobBOSS Report Menu. This is caused by the same faulty UD_report.htm mentioned in the previous error.

Resolution: Download the correct htm file from the JBHELPS website, Support Hotfixes www.jbhelps.com

Support\Downloads\7.x\7.x Hotfixes\UserDefinedLaunchPageHotfix.exe

Logon Failed
Details: DAO Error Code: 0xbd5
Source: DAO.DbEngine
Description: Not a valid Acct. Name or Password

The crystal report requires a secondary security log in when running the report in Crystal, in JobBOSS the report results in the error Logon Failed-Details: DAO Error Code: 0xbd5; Source: DAO.DbEngine; Description: Not a valid Acct. Name or Password

Secondary Log In

What has happened is that the user has used jobboss.mdb as a data source. The user should use the ODBC connection Jobboss32. This has resulted in a mix of RDO & DAO connections to the jobboss database.. To reset the datasource do the following

In the main report go to menu -- Database-Set DataSource Location. A window will open.

Choose the Jobboss32

In the lower pane, open current connections so Jobboss32 is visible. In the upper pane, click on the long path name under the subreport node.

Then click on the jobboss32 in the lower pane. The Update button should activate. Click it. Click close.