Link to home
Start Free TrialLog in
Avatar of TheBrothaULuv2H8
TheBrothaULuv2H8

asked on

VISUAL FOX PRO HELP NEEDED! EASY ONE!!

Ok, our company is in crisis.  We had someone develop some scripts a long time ago in Visual Fox Pro.  The error is really simple I'm sure (I hope) but it's holding up our payroll department!!!

ORIGINAL ERROR:

Error loading file - record number 4.  Form1 <or one of it's members>.  Loading form or the data enviornment : Index does not match the table.  Delete the index file and re-create the index.


That was the original error.  Then I said ok let me try to delete the index file and recreate.  Sounds easy enough.  But I know jack about programming or Visual Fox Pro.   So I poked around and found a EE similar issue where the answer was to delete the CDX files.  

I'm not that stupid that I would delete the files, but I did MOVE the files to another location, then tried to launch it  I got an error.  So I put the CDX files back, but I still get the error.  So now the error is.


TABLE HAS NO INDEX ORDER SET


Please help!!!!!!!!!!!!!

ASKER CERTIFIED SOLUTION
Avatar of CarlWarner
CarlWarner
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of TheBrothaULuv2H8
TheBrothaULuv2H8

ASKER

It appears that you're right on point.  I have after hours of searching found a local guy who's handling it for us.  I'll give you the points because you were correct.  He said the CDX was corrupt.
PS:  If I was smart enought o realize VFP was a database and not a programming language I would have posted it there.  Now I know.  Thanks!
VFP is also a dessert topping. ;)

VFP is an OOP programming language and is a database system and makes a great front-end to any back-end ODBC/OLE DB compliant server engine.

Thanks for the recognition.

[BTW, I hope your help realizes doing a simple REINDEX will at least correct the symptom temporarily and not necessarily fix an index header corruption problem.  We don't knoiw that the index file has that.  But, if it does, it will not go away with a quick and dirty REINDEX command.  The index set must be recreated as a new index set and a brand new file.  Inside baseball stuff, right?]
Thank you for that information!  So far this "consultant" seems to be ok, he claims to have recreated the index set using one of the original files I pulled from an old backup.

Does that sound legit?
It should be OK.  

I was burnt once by using an existing index file that had corruption in the header and it took me more time and unwanted results than I'd like to recall to even discover what the problem was with what looked to be a perfectly legitimate index file.  So, I'm at best sensitive and at worst hypersensitive to index file issues.
Well he hasn't been paid yet I'll run it by him, just to make sure he recreated the file.  That should lead him to believe I'm somewhat knowledgeable on this (when I'm really clueless).  =)
I've confirmed that he recreated the actual files.  Not just a rebuild
That is best.