My apologies for such a nursery-type question on this forum. I have a twenty-year-old British CRM program called ProAction which I use daily and do not want to give up as it continues to be very useful indeed. It uses FoxPro version 1.02 (I'm pretty sure) and runs on a Windows XP SP3 desktop. (I also have a Windows 8 64-bit laptop, BTW, which is why I can't use ProAction on the more modern OS.)
As you will have guessed, the program is no longer supported so I am asking for your advice on how to recover database files following the XP computer's crash. What has happened, and what I have done about it, is as follows: 1. On loading the ProAction program, I got a "Not a database" error message. This had also happened many years ago, and I was given verbal support and told to use one of the files which come with the program, and it worked. Now, having stupidly lost my notes (if I ever made any), I took a guess and used FOXFIX.EXE which seemed the obvious one. This simply opened a command screen which asked if I wanted to overwrite FOXFIX.001. Whether I answered yes or no, nothing happened. 2. I bought DBF Recovery Toolbox and ran it. It "recovered" a number of *.dbf files (but not others: they might have been OK, I suppose). I renamed the old *.dbf files and replaced them with the new ones. Now, on starting the ProAction program I get a "Record is not in index" message. If you click [continue], "Database is not indexed. [Cancel] [Ignore] comes up. If you choose [Ignore], the message says "Error 26 in program ON." (new line) "Database is not indexed." (twice). "Details have been recorded." 3. For info, the "obvious" FoxPro files which came with the program are: FOX.FIX.001 FOXFIX.EXE FOXFIX.FIP FOXFIX.FXP FOXHELP.DBF FOXLAN.BAT FOXPRORT.OVL FOXPRORT.RSC FOXSWAP.COM >From what you can tell, does the ProAction program carry its own first aid kit? Can I repair it "from the inside", as it were? I should say that I have asked this question on another forum and have received very kind and patient advice. Suggestions have included: * Running ProAction in Hyper-V on my Windows 8 laptop (not possible because Hyper-V only runs on W8 Pro or Enterprise). * Buying a copy of FoxPro 1.x and (somehow) reindexing the tables (I simply wouldn't have a clue how to do this: willing to try, but not a very cost-effective option.) * Taking the problem to a FoxPro user group... What would be your suggestion, please? * Can I use any of the files listed above to fix the problem, for example? * In another thread in this forum, I think I detected a hint that you could delete the index files (*.NDX ?) which would then be recreated automatically. Is this possible? I cannot help but feel that the answer is tantalisingly close. And I need hardly say that any advice would be very gratefully received. Please forgive this long post and thank you for reading this far. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/080025BC408C4520815C22ABAF6E3044@acer2013 ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
