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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Indexes key are disappearing!

Status
Not open for further replies.

cparralesl

Programmer
Jan 27, 2002
118
NI
Betreive 6.15
Macola 7.5.103
Sp e

Hello guys,

I need your help with this.

Some tables are losing their index files. I found a procedure to restore them in Technotes directory for betrevie but seems like it is not working. For example: The IMDISFIL table has 11 Fields as index Key 0. More of these fields are gone! and only 2 fields are in the Key 0 now. I have no idea how to fix this up and I am very worry about this becuase most of my crystal reports use this table and its indexes Key. I do not know if this problem will kill the indexes remaining.

As you know, this turn the reports speed very slow.

Also, there is a tool that I have used to make some quick queries that come along Macola, DDF Explorer. With this tool I used to see the tables indexes key, Now I am not. Instead an error message come up saying "Ru-time error 340. Control array element '10' doesn't exist"

The error means that the indexes for the table doesn't exist, I think, and I can not use the tool than before.


Thanks inadvance.:-(



Cesar Humberto Parrales
Application Support
Home : 00505-289-2484
Mobil: 00505-8856-016
 
Btrieve 6.15 is no longer supported and you should probably update to Pervasive 2000. You will finds this a much more stable enviroment. I do not know why you are losing the index files. In Macola under system manager/process/rebuild you will find the files that you want to rebuild. This is supposed to rebuild the table. However I never do this when I am required to rebuild a file I always follow the following procedure.
1. Make sure everyone is out of Macola and stays out during the procedure.
2. Make a copy of the table that you are going to rebuild, (backup in case of problem.)
3. Export the file using system manager/process/export (this will create a file named xxxxxxxx.txt, located in the Macola data directory that you are working in, where xxxxxxxx is the table that you are rebuilding.)
4. Delete the file that you want to rebuild. (This process makes sure that you move the file on the hard drive incase there is a defect on the hard drive.)
5. Initialize the file by system manager/process/initialize.
6. Import the file by system manager/process/import.( You will be asked if you want to append to the file, since you initialzed the table the answer doesn't matter.)
7. Test to insure that everything is OK.
8. Delete the .txt file.

This process works almost everytime. If this doesn't work I sell a utility fo $75 that has never failed and allows you to manupilate the data in the file. This can be extreemely dangereous.

Steve Henley
trianglepartners.com
Exact Software consulting, sales and implementations.
 
You should be able to copy the generic ddfs back from macola electronics into your live data to restore your lost indexes in IMDISFIL. I am curious, though, as to whether you have attempted to modify the ddfs? There are definitely some tricks to this, especially with the older versions of btrieve prior to psql2000i. The macola rebuild or export/import process looks at the ddfs, so if you have corrupted ddfs, you probably won't get the indexes back in the fresh import file. I had modified ddfs at a site once when the ddfs changed during an update. We had to wait modify the new ddfs from the update & to butil save/clone/load due to the sheer volume of records in the file when they could shut down for a day over the weekend. The network fellow decided to rebuild the file when they searched on an index that hadn't been recreated. Result of the rebuild set the ddfs back to vanilla macola current version ddfs. So we lived without our custom index searches until we could modify the ddf again & apply the changes through the butil maintenance process.

If you have modified your ddfs, you will need to recreate your changes to the ddfs & save your data files before attempting to pull the data back in again. Be sure you also have adequate space on your server for your data. You should always have at least twice as much free space as your largest macola file. You should also keep at least 20% free space on the network or performance really stinks.
 
Thanks guys,

Actually, I made a Post few days ago about some Tips about migrating from Pervasive 6.15 to PSQL and I am very thanked for yours answers. The Problem is, as someone said in that post, is not easy to go through.

About whether I attemp to modify the DDF files, that is why we are considering moving to PSQL beacuse even though we do not touche these file to prevent some kind of problems, like this; However, we have some super users that are doing things that we can not make tracking or applay blocks to these files. I have tried to solve this using NT Security but it is not posible becuase come up some error messages about writing rights or others.

Again, thanks for your Tips.

Cesar Humberto Parrales
Application Support
Home : 00505-289-2484
Mobil: 00505-8856-016
 
Humberto,

I think you need to look at going to MS SQL to resolve some of these issues, not PSQL.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
dgilsdorf@trianglepartners.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top