Hi Peter,
This error is usually caused by exported the FRx 6.5 Spec Set to a *.tdb
file and imported it into FRx 6.7. This is not the supported way to
upgrade reports between versions. The reason for this is that Frx 6.5 may
of had 8 tables, but now it has 10 tables that run the report. Since it
was just imported and never went through an actual upgrade it is having
issues running this report. I have listed the supported ways to upgrade
the reports from FRx 6.5 to FRx 6.7 below.
OPTION 1:
Upgrade through regular new version install:
Example: upgrading from FRx 6.5 SQL to FRx 6.7 SQL:
1. Turn off FRx Security in FRx 6.5 (if applicable).
2. Make a backup of SysData directory from your FRx 6.5 install.
3. Create a new SysData folder that will be used for the FRx 6.7 install.
4. Insert the FRx 6.7 CD and install all prerequisites.
5. Allow the CD to find the old version of FRx 6.5 and then select to
update.
6. Complete the install wizard, pathing to the new SysData folder you
created when
prompted. This will upgrade the companies, spec sets and reports.
7. Download and install the latest service pack for FRx 6.7 from
CustomerSource/PartnerSource.
8. Log into FRx 6.7 and verify you can set each Company as Default.
9. Turn FRx security back on in version 6.7 (if applicable).
OPTION 2:
Using Install Assist.exe
1. Make a backup of your SysData directory from your original version that
you are upgrading from.
2. Install FRx 6.7 as a none(new install) install using UNC pathing as
either a Local
Client install or Custom install, creating a new FRx 6.7 directory and a
new FRx
6.7\SysData folder, then proceed with the following:
a. Browse to the FRx 6.7\SysData folder. Locate the file System.cfg and
open
it with Notepad.
b. Remove the [Upgrade] and Syscode= lines from within the
System.cfg file.
c. Save and close the *.cfg file.
3. Browse to the new FRx 6.7 directory, locate and double-click the file
called
InstallAssist.exe.
4. Enter AD as the manufacturing code.
5. Browse to the requested files as prompted by the Install Assist Utility.
First you
will be prompted for the FRxSys32.mdb file from your OLD install (prior
version).
Next, you will be prompted to the FRxSys32.mdb file on your NEW install
(fresh
install) and then to the FRx32.exe on that same NEW install.
6. If the InstallAssist completes normally, you will be able to launch into
your new FRx version and see your reports from your older version available
in your
new version.
Note: if Install Assist continues to fail without errors, enter FRx 6.7 reg
keys prior to running InstallAssist.exe
OPTION 3:
Forced Update:
1. Install new version of FRx.
2. Log in to new install of FRx.
3. Create Companies in the new install of FRx. (must be exactly the same as
in prior version)
4. Create Spec Sets in the new install of FRx. (must be exactly the same as
in prior version)
5. Log out of FRx.
6. Rename the FRxrpts.f32 created by new install.
7. Copy the FRxrpts.f32 from the prior install or from a backup.
8. Log back into FRx and verify the reports are there.
9. Enter Registration keys.
Thanks,
Darian Hanson
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Can ada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.