Robert Kidd Posted June 30, 2004 Posted June 30, 2004 I've had a very similar bug a while ago, is one of you fields that your concatenating together a lookup from another file ? If so try disabling the lookup and try reindexing your field
N Hagy Posted June 30, 2004 Author Posted June 30, 2004 Yes I am concatenating lookup fields from another file and yes your suggestion worked. Thanks. I was using the concatenated fields to check for duplicates. I was hoping the the indexing would remain after I re-enabled the lookups but they reverted back to an unstored value. It's as if the lookups are being treated as related fields. Is there a fix for this??? Again, thanks for your help.
Robert Kidd Posted July 1, 2004 Posted July 1, 2004 It's clearly a bug that somehow affects certain files under certain conditions. I can't remember if this worked but try the following:- If your fields are called FieldA and FieldB create fields C & D which are calc fields and simply equal Fields A and B respectively. Try indexing these new fields, if this works you should be able to concatanate C & D together to give the result you originally wanted
N Hagy Posted July 2, 2004 Author Posted July 2, 2004 Robert Tried your suggestion and got the same results. The calc fields responded same as the lookups. After setting them to store they revert back to unstore once I close the define fields window....thanks for trying.
Recommended Posts
This topic is 7711 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