Thank you all. I did just that lbass and am hoping that she agrees to it. Sure makes things a lot easier for me. And as fields change, so should that table - wouldn't they? If we use hardcoding, we may eventually drop data off without realizing it.
I feel better about my decision, but she...
switch ({employee.BU}={unit.BU},{unit.name})
= I get the BU but not the name. It would be perfect if this would just give me the little words in there.
I have been told by our IT guy that the best way is to add the table a second time. (I personally think this is reasonable) But somehow...
I had a couple of reasons given to me, but can't really get into it here... I am just unable to go about it thoes two ways. No hard coding the Units and no second tables. Sorry. They are very good work arounds - I think.
Thank you for your suggestions.
I am already pulling information from the Unit table into the report and linking it on an account field. If I link back to the employee table it sets off a loop and gives me data for all employees attached to that branch.
master.BU = 10,11,12,13....
employee.BU = 10,11,12,13....
Unit.BU = 10,11,12,13...
Unit.name = XYZ, LOL, OMG
switch ({master.BU}=10,{employee.BU})
join is on master.EmpID to employee.ID
So if my BU = 10, I need it to look at the employee.BU table and use that field as the new BU with the...
I have a field {table.field#} with a value in it that I am trying to spred into other groups.
This works (but...)
switch ({table1.#})=###,{table2.#})
...but now I am trying to make that value = to a name field in table2.
so, really: How do I assign that # to = to a string from table2?
Any...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.