Jan: The same thing happened to me! One client asked me to generate an invoice# that was the custid followed by the date as you have it. Of course I made the column integer without thinking and had the same problem you did. I changed the column type to be Text instead.
Karen > I had my own little challenge to figure out today. > I have a process that has run consistently for about a year in 7.6. > Today the client received error messages. After some question asking > we determined the that the errors were around 5 customers with custno all in > the series > 3850, 3860, 3865, 3870, 3875. > The offending code was > SET VAR vInv INT = .vInvText > vInvText was generated as (CUSTNO + DDMMYY) so the invtext for one of these > would be > 3860020309. > At first glance I couldn't see what was wrong with this. After mulling a bit > over a sandwich > I decided to check what the data type of INTEGER was is as follows; > Holds whole numbers in the range of ±1,999,999,999. So I lined up my > numbers. > 1,999,999,999 > 3,860,020,309 > the number was too big. Had to tell the client to change his customer > numbers > to realign with this process. > > Jan >
