Sage 100

unless I am misinformed custom office UDF's with a numeric field type are limited to 3 decimal precision (REALLY????) Anyone know of a way around this? 3rd party enhancement or otherwise? I'm considering making it a string so the user can type more characters, but then I will have to convert it to a numeric field every time I want to do anything with it in crystal. I actually need this at two different clients, and one of them needs the UDF to be picked up by WOScan so that means that if I use a string there, WOScan will have to modify code if they want to use the field.

I think I have changed the mask to more than three decimals successfully. It worked for me. https://90minds-com.socialcast.com/messages/24252494?ref=stream

when I expand it past 3 decimals I get the attached message. I assumed from the message that it would not store anything beyond three decimal places, but I'm going to test it now to see if it holds the extra decimals.

Ditto Therese, but I think there is a limit.

ok I guess I should have tested this before posting - I just did 6 decimal places and added it to CI_Item (which is where I need it in one of my client sites. I stored a number out to 6 decimal places and saved the record and pulled it back up - all 6 decimals are there so it appears to work. I don't know what ever possessed me to take a Sage message at face value.

Were you able to display the number via a query or via a UDF link to another table? Perhaps there is a data dictionary limitation. If not, maybe the guy with the long finger nails that @AlnoorCassim referenced yesterday was behind this WAD.

I think it is a bogus error message. I have seen it before and the UDF worked at 6 decimals for my customer as well