The chief cause of this type of thing is Irregular Shutdowns of the system hosting the application and/or the tables. (There are other causes but this is the chief among them I believe) Usually you will see the index files getting corrupted, but I have seen this with tables and with memo files as well. The problem is lessened a good deal with VFP, but it still can occasionally happen. In either event, I applaud your decision (or management's) to convert the application. If you do a Keyword search on this forum you should find quite a few threads/posts on how best to prevent and deal with this. In the case you have presented I would say that you may need a hex editor of some sort so you can shift the bytes right or left until they line up with the columns, but this is a last resort and may or may not work depending on the level of the corruption. Other automated programs you could use to try and fix your data are FIXFOXPO.EXE, SALVDBF.EXE, and FOXFIX.EXE - these are a few that I know of off the top of my head that will work with free tables. Sorry I don't know the links for downloading them also, but a search on Google or this forum should yield some links for you. You may also get some semi-acceptable results by pouring the data from the corrupted table(s) into a blank table(s) given that you are able to still open the table(s).
You will also find some threads/posts dealing with the best way to convert...having done a number of these myself I can tell you that you will want to do a Visual conversion as opposed to a Functional conversion and then cut and paste your code into the appropriate events, methods, and procedures. There are a number of other things to watch out for and plenty of tips-n-tricks when converting a FPW app to VFP so read up on it and it will save you time and headaches later (if you already have then consider this my confirming of what you already know).
Slighthaze = NULL
[ul][li]FAQ184-2483
An excellent guide to getting a fast and accurate response to your questions in this forum.[/li][/ul]
