Reports are missing after installing or upgrading FRx

Entry Type: Informational

Product: FRx

Application: FRx Desktop

Version Reported: 5.5, 6.0, 6.5, 6.7

Subject:

Reports are missing after installing or upgrading FRx.

Possible Resolutions:

If  FRx has been upgraded and the old installation is still intact:

Resolution 1:

  1. Launch the old version, select Company / Information and make note of specification set names being used for each company.
  2. Select Company / Specification Sets and make note of  location and file name the specification set is saved in.
  3. In the new install, copy the file noted in step 2 into the new SysData directory.
  4. Go to Company / Specification Sets and set the specification set location to the new file.  If the specification set does not exist, select 'New' and create the specification set with the correct file location.  A message may appear stating that the spec set exists in the new location, and asking if you wish to overwrite. Select 'No'.
  5. Go to Company / Information and select the specification set noted in step 1.

Resolution 2:
See How to upgrade FRx manually.

If FRx has been upgraded but the old installation is not intact:

  1. Select Company / Information and verify the correct specification set is being used.
  2. Select Company / Specification Sets and verify the location of the specification set is pointing to correct file.
  3. If these options appear to be correct and no reports exist, e-mail the *.f32 file to Customer Support at [email protected]  for review.

If FRx is installed on a new computer with an existing SysData directory and reports are viewed on other computers:

  1. Select Admin / Organization of the new installation and select 'SysData'.  Verify the location is correct.  If the location is not correct browse to the correct location and select 'Update Current User Only'.  If the new location is not saved when entering FRx, see Changes to the location of the SysData directory are not saved.
  2. If the location of the SysData directory is correct and reports are still not appearing, select Company / Specification Sets and check the location of the specification set.  If the location is the "C" drive of the local computer, then place the *.f32 file in the shared SysData directory and change the location of the specification set to this new location in Company / Specification Sets.
  3. If the SysData directory, specification set name and location are the same and reports still do not appear and mapped driving is being used, verify the mapped driving is set up the same on both computers. 

If FRx is installed on a new computer with an existing SysData directory and reports are not viewed on any computer:

Resolution 1:

  1. Select Admin / Organization, select 'SysData' and verify the location is correct.  If the location is not correct, browse to the correct location and select 'Update Current User Only'.  If the new location is not saved when entering FRx, see Changes to the location of the SysData directory are not saved.
  2. Select Company / Information and verify the correct specification set is being used.
  3. Select Company / Specification Sets and verify the location of the specification set is pointing to the correct file.
  4. If these options appear to be correct and no reports exist, e-mail  the *.f32 file to Customer Support at [email protected] for review.

Resolution 2:

This issue occurs with FRx Version 6.5 on a FAT Client installation with Sysdata shared on the network. During the installation, instructions will prompt to enter or browse to the new location of the Sysdata directory. If the directory is pointing to the existing Sysdata directory on the network, the reports will be overwritten. As a precaution, install to the local drive of the client workstation during the install and browse out to the Sysdata directory after the install completes and FRx Designer launches successfully.  See 'How to install FRx 6.5" for more instructions.
Note:  In FRx Version 6.7, changes have been made to allow the Sysdata directory to point to the existing Sysdata directory on the network during the FRx client install. This version will not cause the reports to be overwritten.

Notes: