![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
These Serial Numbers actually pertain to customer farecards serial numbers encoded on them that they use on the bus& subways here in new york city and the problems occurred suddenly in the 2140000000& 2150000000 ranges, until we found the breakpoint where it actually happened. |
#3
| |||
| |||
|
|
On 2/10/2011 6:51 AM, George Lewycky wrote: These Serial Numbers actually pertain to customer farecards serial numbers encoded on them that they use on the bus& subways here in new york city and the problems occurred suddenly in the 2140000000& 2150000000 ranges, until we found the breakpoint where it actually happened. User-defined data really shouldn't be used as a unique serial number, but that's another matter at this point. I would change that field to be a text field. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Howard Schlossberg FM Professional Solutions, Inc. Los Angeles FileMaker Certified Developer Associate Member, FileMaker Business Alliance |
#4
| |||
| |||
|
|
Thanks for both of your replies I received another reply and they suggested making it into a date. I'm going to try those ideas....... These Serial Numbers actually pertain to customer farecards serial numbers encoded on them that they use on the bus & subways here in new york city and the problems occurred suddenly in the 2140000000 & 2150000000 ranges, until we found the breakpoint where it actually happened. It even happened on the IBM Mainframe until they redefined the field and expanded it a digit which we cant do in Filemaker!!! I had another idea of using Excel to create the sequences and copy & pasting them into Filemaker but it didnt work either. Also another idea of making it like a formula in a Excel cell.. I'm probably meeting my Filemaker users group in NYC Tonite and they might have some alternatives also George. My earlier answer was a FIRST GUESS. |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Hi everyone & thanks for your feedback: we have farecards and the field in question is actually its 10-digit serial number which are sequential. In a nutshell we reached the maximum value of the 10 digit numeric field that Filemaker can compute with. And once we add past that number the results are coming back negative. I know we have an old version and yes we dont have every single serial number on the database We are in the midst of replacing it with SQL Server and Visual Basic and the Filemaker application has alot of bells and whistles and this problem came up on other systems but they were able to add a digit and/ or remove the sign bit but we dont have that capability now. email me at george.lewycky (AT) nyct (DOT) com and ill send you screen prints illustrating it more I was just at my FM users group in NY City last nite and they suggested using 2 global containers and compute it that way among other ideas......... George |
#7
| |||
| |||
|
|
In article 6feee9f0-4376-4500-8814-288cbffa17ad...oglegroups.com>, George Lewycky <grlewycky (AT) gmail (DOT) com> wrote: Hi everyone & thanks for your feedback: we have farecards and the field in question is actually its 10-digit serial number which are sequential. In a nutshell we reached the maximum value of the 10 digit numeric field that Filemaker can compute with. And once we add past that number the results are coming back negative. I know we have an old version and yes we dont have every single serial number on the database We are in the midst of replacing it with SQL Server and Visual Basic and the Filemaker application has alot of bells and whistles and this problem came up on other systems but they were able to add a digit and/ or remove the sign bit but we dont have that capability now. email me at george.lewycky (AT) nyct (DOT) com and ill send you screen prints illustrating it more I was just at my FM users group in NY City last nite and they suggested using 2 global containers and compute it that way among other ideas......... George I don't know about the limitations on the old version of FileMaker that you are using. The specs for FileMaker 11 say that number fields can deal with 400 (four hundred) significant digits. See http://help.filemaker.com/app/answers/detail/a_id/7541 You might think a little harder about moving away from FileMaker, and instead consider upgrading to FileMaker Pro 11 and FileMaker Server 11. |
#8
| |||
| |||
|
|
On Thu, 17 Feb 2011 13:35:13 +1100, John G wrote: Older versions of FM, at least Ver 5 and earlier, seem to use a 4 byte integer in the calculation of serial numbers to insert in the REplace Field Contents with Serial Number. This fails at 2147483647 plus one. All other arithmetic and number storage appears to use Real or Floating point math and so works fine. No, some versions in between 5 and 11 can't deal with 16 digit numbers, such as credit card numbers. - Martin |
#9
| |||
| |||
|
|
On Thu, 17 Feb 2011 19:26:18 +1100, John G wrote: No, current Filemaker can deal with 800 digit numbers but only indexes 400. Credit cards are not numbers. They are 3 or 4 seperate fields with dashes between and if you strip the dashes and do any math you will have an invalid credit card number. Is that so? The companies I know just take the 16 (+3) numbers, regardless of dashes, spaces or anything else. |
|
The biggest Credit card number I have seen is 15 digits and 3 dashes and even FM 2.1v3 could handle 16 digits but as I said you cannot do math on credit card numbers. I'll check whether numbers are different in other countries. Here it's 16 digits both for Visa and MasterCard. I stand corrected about Credit cards 16 is correct. But I checked the length for FMP 6: numbers: 120 digits text: indexed are the first 20 digits only. For FMP 7: numbers: 199 digits text: indexed are the first 109 digits only Are you sure about your 400 digits named above? Certainly for FM 7 I can't find 6 specs. |
#10
| |||
| |||
|
|
On Thu, 17 Feb 2011 19:26:18 +1100, John G wrote: No, current Filemaker can deal with 800 digit numbers but only indexes 400. Credit cards are not numbers. They are 3 or 4 seperate fields with dashes between and if you strip the dashes and do any math you will have an invalid credit card number. Is that so? The companies I know just take the 16 (+3) numbers, regardless of dashes, spaces or anything else. The biggest Credit card number I have seen is 15 digits and 3 dashes and even FM 2.1v3 could handle 16 digits but as I said you cannot do math on credit card numbers. I'll check whether numbers are different in other countries. Here it's 16 digits both for Visa and MasterCard. Yes you were correct about Mastercard and Visa but I must have |
![]() |
| Thread Tools | |
| Display Modes | |
| |