Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBase IV will not Reindex

Status
Not open for further replies.

HJS3105

Programmer
Apr 25, 2007
1
US
I am running DBase IV on Windows 2000 and have a very difficult time reindexing. Every so often it will do so but most times not. Anyone have any advice ?
 
Could You post a Code sample of what is not working?


David W. Grewe (Dave)
 
Reindexing with DB5 I had similar issues. I had to create a partition 4 gigs or less, because anything larger caused it to say not enough disk space, but only on a network drive. If I reindexed on a local drive it was happy.

Thanks,
ChaZ



There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
 
Are you using disk compression? I seem to recall that dBase 5 on a Netware network with disk compression caused problems. I had to access the index file twice to force decompression so it could be saved again.

Not sure about dBase IV.
 
I use dBase IV for DOS with 5 clients. They have been running my program in a DOS window in XP with no problems.

One client's PC crapped out and she bought a new PC with Vista. My program worked on her machine in a DOS window for a while (1 month) and now has started to have major issues. USE-ing any DBF brings up an error message saying the MDX file is corrupted. It will not allow reindexing.

Even working from a dot prompt causes the same problem.

Does anyone have any suggestions?

Thanks

Wayne Gossett
 
First, make backups of current tables. Next, go back and identify the most recent valid copies. Open that table and view the index structures, the tags and tag expressions.
Code:
USE TableOK
DISPLAY STATUS
Now, one way is to open the latest table and delete the tags and recreate the tags. Option B may be the cleanest way.
Code:
* Option A
USE TableBAD
DELETE TAG TAG(1)  && repeat until all tags removed
USE

* Option B
ERASE {TableBAD}.MDX
USE TableBAD  && get error no Production .MDX found
              && so click on Proceed to clear .MDX link
Now build a new MDX with the tags and tag expressions.
Code:
USE TableBAD
INDEX ON {tagExpression} TAG {tagName}  && repeat for all tags
USE
Of course, this is just one way to do it, and you still have the issue of why the tag indexes get corrupted.
 
>>HJS3105 >>

I use a dBase IV on XP Pro with 300,000 records. I use mdx and single indexs. Never had a problem. We use everthing from a single to a compound index. We are very heavy into indexing.A little more information and we might beable to help.

Bob
 
Dbase 3 had indexing problems on very large disks because its calculation of free space on the drive is outdated, and it thinks there is no space.
Does this issue persist into later versions?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top