Sage 100

Any FRx guru's? Client had a server crash (they weren't backing up the sysdata folder), sent the drive out to recover, got the data back. but...when I try and open FRx, I get : FRx Run-time error '5'; Invalid procedure call or argument. Only option is ok and that closes the program. Can't get in to rebuild the database. Anyone have any thoughts?

Hi Diane, I would do a fresh install of FRx, grab the frxrpts.f32 file from recovered sysdata and put into place. You may need to create the companies again.

Ok somebody, make a wisecrack but www.eversafe-backup.com

Agree with @NancyHanson, locate the old FRx CD AND all the service updates AND the secret patch if the computer is 64 OS and put in a fresh copy. Hopefully the sysdata folder is located on the server so those the data files weren't affected.

if the sysdata was on a network mapped drive, you have to have the same mapping. there should be in ini file somewhere on the workstation that FRx is installed on - in program files\frx Software (I think) that would have the drive mapping described. Once you have that set up Frx should work.

I have verified that the path is correct, the FRx works fine with another sysdata folder, it's their data that is corrupt. Unless I can get their data to at least open, I can't get in to rebuild. The old knowledgebase mentioned a utility that Sage had to rebuild the data externally, but naturally calling Sage isn't going to help. I even tried to use the SMI conversion utility on it, but that didn't work either.

Have you tried copying from old sysdata folder just the frxrpts.f32 file to your newly created sysdata folder?

Yes I did that, same error

Have you tried a Google search?

Can you 'x' out of the error message and then try this..........

No, when I get the error it just closes FRx

Unfortunately, sending a drive out for recovery, doesn't mean it comes back 'as good as new.' There is a good chance of data loss on various sectors of the drive and the underlying FRx files may simply be damaged beyond repair and may require reinstallation and recreation of the reports. The price to pay for poor backup practices but you can't get blood from a stone. I hope I'm wrong but this isn't smelling ood

With new install (blank frxrpts.f32), can you launch FRx and select a demo company, then try to import the spec sets from the corrupt one? or with corrupt one in place in the new install, can you select a demo company and try to export the spec sets?

Resolution: we were able to rebuild the files in Access. Most of the data was able to be recovered, we did lose some detail lines and some accounts, but when faced with recreating reoprts for 35 comapnies, we are much further ahead. Thanks for all the input everyone! It was much apprecaited.

Are they backing up the sysdata folder now? :-)

If they aren't - they will be once they get our bill!

Hopefully, you have it stored on the network so it is easier to backup. Might be time to sit down and have the ""S"" conversation....... ""S"" as in SI.

Diana, were you able to rebuild in Access or how did you accomplish the rebuild? Glad to hear you were able to get it back up and running.

The main FRx file - frxrpt.f32 can be opened in Access. It is password protected, but you can google the password. Then rebuild.

Thanks, @debbiebeach above. I was getting this error upon trying to specify the sysdata path on a new computer. Once I first selected the FW company upon launching FRx, the error didn't appear. Initially I was just bypassing the company prompt.