Updated to 5/1/07.  My users have been getting sporadic errors as follows:
 
When some people are in IN-A, they enter a part #, it rebuilds the stock info, then they click on
the button for sales orders and they get this error:
WARN ERR:  File WBLOOKUP: SRC LINE 421
The array brackets [{}] are not matched   (and then there some garbage type characters after that)
 
 They click on OK and they get
WARN ERR:  File WBLOOKUP: SRC LINE 421
There is a fatal problem with the following expression. The problem may have to do with the parentheses: {
 
They do get the sales order lookup, and then if they scroll they get the error
WARN ERR:  File WBLOOKUP: SRC LINE 1012
The parentheses are unbalanced in this expression.
 
The other error we've seen in IN-A is
WARN ERR:  File WBLOOKUP: SRC LINE 421
There is a fatal problem with the following expression The problem may have to do with the parentheses:
BKARINVL.PQTY <> VAL ("0"                      ) .O.BKAR.INVL.UBO     <> VAL ("0"
)
 
And finally, when using the drill up from a BOM lookup in IN-A, one user just got
FATAL ERR - File ISUDF.SRC Line: 132
The field you are trying to use is unallocated.  It may belong to a file that hasn't been opened yet, or was an array that was removed from memory - BKAP.POL.PCODE.
 
I copied all the BKLUGRID.* from DBAMFG to the DRILL subfolder, but we still continue to see these  
errors.  Again, they don't happen all the time, just some of the time, maybe after several times doing the same task in a module.
 
????
 
TIA
 
Val

Val,
 
  I have been working on the lookups and Lynn will be putting out a patch later today that may fix this issue. I do find it odd that only you are getting this error (or at least you are the only one reporting it) so something must be out of whack.
 
The error you are reporting is with the GUI lookup screen, so yes running the old BKINA will remove the error, but you will lose the features of the GUI screens. (filters, printing grids, notes, evolinks, drill downs, substring searches etc...)
 

I rolled back the T7 stuff after one week with the 2/14/07 update and am still waiting for the kinks to get worked out before I dare have suers try it again.  I concur that things work well at the easy pace I use when testing, but lose stability when users try to force it into the Classic mold. Many feature improvements/additions have been made and I think I can manage the change, so long as the feature loss is minimized. People don't mind change so much when new things are added, but they seem to blow their tiny little gaskets when options (even poor ones) are dropped.

We also tried out the T7 apps and no longer use them. I'd like to because they look better and have more features but, once again, the users don't like them and are able to cause trouble with them. It's tempting to blame the end user but if the end users in THREE companies can't do it then you have to see the trend. After a while you have to quit blaming the end user and start looking at WHY everyone seems unable to really get into the new version. Maybe the T7 apps just don't have the same flow, maybe they work too slowly. Let's put it this way, if the program screws up because of impatient users then it's STILL the program's fault. No question. If it doesn't work at the same rate as the user then it's WRONG. I don't care how much time anyone put into it or how great it works for other people if it can't keep up with someone then it's not right. One of the cardinal sins of user interface design is creating an application that forces the user to slow down. To be effective a GUI must be realtime. Any lag is seen by the end user and they won't be liking it. That said, I do like the new T7 versions and I think they are going down the right track. But apparently they may not yet be ready for general consumption. I'm sure they'll get there eventually though. Just remember IStech: SPEED, RESPONSIVENESS,SPEED,SPEED,SPEED.

Yeah, I'm the same way: I like newness for it's newness. I like cool new gadgets, new software versions, and just released games, cd's , and videos. So I *do* like the T7 versions and I am willing to live with the sometimes slower response. But statistically a lot of people want stability and familiarity.

Well, I posted my errors, nothing new on that front.  As for newness, for the most part
the users here have been pretty good about changes.  For whatever reason this last set
just flipped them out, maybe because it was a Monday, I dunno.  
 
I agree if people are able to "break" the apps using them, then something isn't right, no question.
At least I could roll things back, now they're happy clams.
 
I'm not sure which buttons caused the slowness.   I'll see if the users can recall anything specific.
 
Val

One option to consider - given the flexibility of the Evo menus - give users both flavors of the programs - then they can use the GUI (we will never work out all the kinks until people start using them) but if something frustrates them, they can go back to the old to do what they need to do and be less frustrated when they complain that the GUI doesn't do it.

What was the outcome to these error messages?  Did everyone just revert to pre-T7 files?