Sage 100

Interesting issue that I just ran into on v4.4 PU5 - this is probably a well known issue that everyone except I has encountered. If you create a UDF with the same ODBC name as a key field --- in my case Department which I was trying to use in a PAYROLL EMPLOYEE MASTER UDF -- it won't work. Actually it will create it... No warning. You can place the UDF on the custom panel. You can add values to it. So far as I can see extracting info from that UDF via ODBC is a no go - instead what it does is it transfers the key field value or probably more accurately as you fill in the info on the custom panel -- the Department # is over-written without warning by the real department (as part of employee master) Should warn you that you've created a duplicate field. Go ahead and laugh. Countdown to ""oh I've known that since 1980"" ... 3-2-1....

Could be one of those ""Easter Eggs"" left over from the 80's when they wrote the original code............. Good to know though!

That's really odd, because the field names aren't actually the same. The UDF should be ML_UDF_DEPARTMENT, or some such thing, not just Department. And of course in Payroll it's stored in a completely separate file yet. So DOUBLY weird.

For ODBC purposes the ML_UDF is separate. I didn't dive into the underlying file contents -- I suspect the contents are ok and it's the ODBC that wrecks.

BAD ODBC! No crunchies for you!