c.reid

Confirm that iscr32.exe is working by itself e.g. iscr32.exe -k10 -r1500 myfile.pro
Ensure you path includes the location of the executables

There is another option that works with iscr called -e (empty). you could give that a try.

-e didn't seem to do anything at all. I appreciate all the help, I feel as if there may be nothing I can do to get the database back up and running. the only other thing I was thinking is you mentioned originally that "it looks like your proiv is set to check the files at launch" is there a way I can tell it not too? and hope that it gives me access to some of the data?

You have to perform the procedure I documented previously (iskeys, isout, iscr, isin). That 'should' recover the file. Failing that you may need to call PROIV direct, as they can repair bad index's.

ok, i am getting an error during the iscr phase regarding both files. all the steps before and after that you mentioned are working fine though.

running the command "iscr32.exe -k47 -r3000 e:\pro4data\inwrk1.pro" (for the first file) yields an error message of "iscr: error creating e:\pro4data\inwrk1.pro; FS_UNEXPECTED: Unexpected error conditions. [134 - Can not get the request handle pointer]."

any additional magic you may know of that can fix this? i did run the ischk.exe after i did the steps but I still get the exact same error log at login, i assume because of the iscr error i am receiving. i feel so close to fixing this.

You have to perform the procedure I documented previously (iskeys, isout, iscr, isin). That 'should' recover the file. Failing that you may need to call PROIV direct, as they can repair bad index's.

Somehow I completely missed that initial post and only saw the second. Thanks so much, I'll try it out and report back.

Actually I figured it out. running the command from within the scsbin folder and pointing it at the offenders.

it found the errors in inwrk1.pro and i hit yes on rebuild and it said unable to rebuild now what?

Reading your post more carefully it appears that the offending files are inwrk1.pro and rspfk3.pro that are located in the PRODATA directory. The procedure to correct these is the same. I would also run the ischk against all the ISAM files to ensure no others are corrupted. i.e. ischk.exe *.pro You can use a -y option and that will force the utility to attempt to auto correct the data.

Regards

Darren

Thanks so much for your reply. Am I running ischk.exe *.pro -y from a command line, or is there a utility within the SCSBIN folder that I should be looking for?