Thanks for your comments, Chris, but I have already resolved the issue. The most interesting thing I learned from this experience is that the PB development environment vs. compiled (M-Code) reacted differently to the same program code. Specifically, I had a PB variable defined as a "Long" and the "problem code" was taking a number string and explicitly converting the number string using the Interger() function and assigning it to a "long" variable. In development, PB apparently overrode my explicit conversion and treated the number string as a long value (again, since the variable was a long...). In the compiled version, PB took my "explicitly" converted number string and transformed it into an integer, THEN assigned the converted integer (now a negative number) to the long variable. It had me pulling out what little hair I have left, but, in the end analysis, it was my mistake (or oversight since this number was originally designed to be an integer value) and once my client exceeded the highest value that PB recognized for an integer, I had to go back and re-code a lot of my application, I just overlooked this one conversion....
↧