NuttyMoose Posted June 14, 2004 Posted June 14, 2004 I had a great working database...but then all of a sudden CRASH...now it says index missing on some of my fields...how can I correct this? HELP Brahim
Tripod Posted June 14, 2004 Posted June 14, 2004 Have you tried to recover the file? I think this may rebuild the indexes. Or, you might try turning the index off, closing the file, opening it, and turning it back on, etc.... To recover: 1. Choose File menu > Recover. 2. Select the file to recover, and click Open. To turn indexing on and off, go through define fields, select variable, press options, press storage options, turn off storage to turn off indexing. Good luck, I wish you well. If this doesn't work, try saving a clone and importing the data from the orig. file into the clone. --Tripod
RalphL Posted June 15, 2004 Posted June 15, 2004 Check your relationships. I had this show up today when I used a bad relationship.
NuttyMoose Posted June 16, 2004 Author Posted June 16, 2004 Thanks Guys... No luck....I restored from a backup from 1 week ago... Why does this happen... It all was working fine then WHAM error and I had to close...then when I reopened... crap... Thanks for the help... Brahim
NuttyMoose Posted June 18, 2004 Author Posted June 18, 2004 Sorry for the delay...I was outof town... The database is on my local harddrive.
Clinton Posted June 27, 2004 Posted June 27, 2004 I ran into this problem as well - it would appear that it occurs if you are trying to use an unstored value as the match field for your relation. So, check and see if you went and changed any of your Indexed fields into Unstored, calucated fields.
NuttyMoose Posted June 28, 2004 Author Posted June 28, 2004 WOW...I will try that...thanks for the help. Brahim
wmugrad28 Posted January 6, 2005 Posted January 6, 2005 I had the same problem with a portal showing index missing. Is there a work around for this other than turning off the "unstored" part of the value? I need that for a calculation I'm doing. Second, when I do take that off to see what happens, my portal is populated with 13 of the EXACT SAME record. I have 13 records in my related table. Each portal should only have 0-4 records (all different) in it. Ideas? Greg
-Queue- Posted January 11, 2005 Posted January 11, 2005 If your child key is unstored, then you will not be able to create a viable relationship. Is there a chance you could script the key to be set whenever one of the fields the calculation references changes?
Recommended Posts
This topic is 7519 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now