Zugg Software :: View topic - #find - Columns request returning different Columns {SOLVED}

Beginner Joined: 15 May 2012 Posts: 15

I've got 11 views besides the ALL view including--- Potions, Spellbooks, Weapons, Containers, Other, Wands, Armor...

I've got 150 or so fields for things--- Str, Dex, Weight, Charges (of wands/staves), Pages (of spellbooks), Farsee... These fields are Booleans, number fields, option lists, etc...

Column one is ROW 0, 1, 2, ...
Column two is REC 1342th, 1343th, ....
Column three I have as TYPE (Treasure, Money, Key, Container, Weapon, Trash, Potion, Scroll, Food, etc)
Column three I have as SLOT (Hold, Shield, Attach belt, Body, Wrist, Neck, Ear, etc)
on and on through the 150 fields.

#FIND Money
This should filter first column TYPE for money but tries to filter Neg_Shield, a Field about 75th on my list of fields.
#FIND Money all type
Same deal. This should filter first column (type) in (all) view for (money) but same result
#FIND Money all slot
This works. This filters TYPE Column into all the Money items in the ALL view.
_________
#find 33 all moves
This should filter MOVES column, ALL view, to just the ones showing 33, but it comes back with NAME Column, ALL view, 33 filter with no results of course.

etc etc al

Why am I getting these results? Seems like its all mixed up on the Column. I type TYPE and I get Neg_Shield Column. I type SLOT and I get TYPE column. I type MOVES and I get the NAME column. and so forth.

Thanks

Beginner Joined: 15 May 2012 Posts: 15

Maybe I explained this to complicated.

#find 33 all moves

33 -- the value I am searching for
all -- the view I am looking in the database views
moves -- the field I am searching for the 33 in

it all works as expected except its not looking in the MOVES field, its looking in the NAME field.

So my question is why is it looking in the NAME column?
.............................................
Now, if I change the #find to this:
#find 33 all slot

The SLOT makes it look in the TYPE field. It seems every Field relates to a different (but specific) Field.

I guess I could do a chart and match which columns reference which columns and use those in my queries
Name = Moves, Type = Slot, Location = ArmorClass and if I wanted to look up items from location 'Keep of Evil' I would do:
#find "Keep of Evil" all ArmorClass

Is that the best solution? This isn't a deal breaker, I can do that. Just was curious if someone had an idea or not why.

Beginner Joined: 15 May 2012 Posts: 15

I went to the Fields tab on the database and looked at all the fields. The default (#find whatever) was searching Neg_Shield. So I highlighted Neg_shield and clicked on Move down a few times and ran the #find again. Now #find whatever was trying to filter from the Prot_Undead field. So moving the fields up and down on the list affect's the #find. Now to figure out how I can either reset or move things around to work...

But the way it looks is that its thinking the default (1st column) is really the 80th or so column no matter what the column or column name is. I can move all the fields around, but whatever is sitting in that 80th column will be considered 1st. Any help or suggestions would be useful.

thanks

Beginner Joined: 15 May 2012 Posts: 15

OK got it "fixed". in the FIELDS tab I took the list of all my fields on the left and moved them up or down to the spaces they wanted to be in. If I had put in TYPE and it gave me NAME, then I moved TYPE down or up to where the NAME was sitting on the list. I did that with all of them, although it turned out only about 10 or so had to be moved. Those were the 10 or so that I had moved up or down the list for convience sake at some point. They threw everything else out of whack, but when they were moved, everything else got in its correct order too.

So moral of the story, once you make a field, do not move them up or down on your list. The buttons and such are bugged in such a way as to make the FIND command not work.

To my knowledge, this doesn't effect Views, so on the views I can organize my fields/columns anyway I want too. Just in the fields tab and the list of fields, they are in stone on where they are on the list. Which is fine, a little inconvienient for grouping purposes, but fine because it doesn't effect the views or dbase in anyway that I see so far.

Thanks Kohl for your help.