Just discovered a gotcha using KixStrip400 (we're using versions 3.20e). [Frown]

Using Kixtart 4.02 and the & operator to perform a bitwise AND as follows:
Val(@PRODUCTSUITE) & 16
KixStrip400 removes the spaces surrounding the & and Kixtart interprets the &16 as a hexidecimal number. Under certain circumstances this throws an exception error because there suddenly appears to be no operator between Val(@PRODUCTSUITE) and &16.

Workaround has been to change the order in the expression to:
16 & Val(@PRODUCTSUITE)
This appears to work even after the spaces surrounding the & are removed. [Smile]

What have others experienced?

MCA will probably want to rectify this so that others aren't bitten and spend sleepless hours wondering why. [Wink]
I wish Kixtart didn't uses a single & for both denoting a hexidecimal number and the binary AND operation Too late to change now and maintain backward compatibility I think.

-Jon