Variable limits

[faldo]

Heya,

I'm trying to figure out how to work around a problem with the limitations of variables and would like some help.

I've extracted a number from a database with an SQL-UDF as follows:

$iRval = _SQL_GetTable2D(-1, "SELECT table FROM database ORDER BY id", $var, $iRows, $iColumns)

This results is an array of variables and the one i need is a value with 26 numbers.

When i call on this value, the value seems to big for a variable and the result is flawed.

As demonstration, the same problem occurs in the following example:

$var= 11111111111111111111111111
MsgBox(0, "", $var)

The message box doesn't display 11111111111111111111111111 unless i make a string out of it.

Thankfull for any suggerstions.

Cheers

Edited February 9, 2012 by faldo

[Melba23]

faldo,

Do you want to display the big number or actually do some operations on it?

If the former then you already have the solution - if the latter then the BigNum UDF might be the solution. I have no experience of using it myself - please let me know if you find it useful.

M23

[BrewManNH]

Is the 26 digit number actually a number or is it a string made up of numbers? Because if it's a string made up of numbers, you should be referencing it as a string. If it's an actual number you should use scientific notation to reference it.

Sounds like a 26 digit number is too large to display using even 64 bits.

[faldo]

Thanx for the quick responses.

The following code displays my use of the variable ($var):

$iRval = _SQL_GetTable2D(-1, "SELECT table1 FROM database ORDER BY id", $var, $iRows, $iColumns)
$hData = _SQL_Execute(-1, "SELECT table2 FROM database where id=" & $var[1][0])
_SQL_FetchData($hData, $aRow)

$var[1][0] contains a 26 digit value and everything seems OK after the first line but when i use this variable as reference to get data from another field i get the same behavior as i get when trying to display a 26 digit value in a messagebox like the example i showed above.

If i could somehow convert the value in $var[1][0] to a string my problem would be solved.

@BrewManNH: the 26 digit number is a value from a field in the database, with value i mean 1234 as compared to the string "1234".

@Melba23: i want to use the variable in another operation but it seems it gets distorted due to the maximum value-limit in a variable.

Edit: Btw, if the data in the DB-field contains a value of 10 digits, i don't get any problems, that's why i narrowed it down to the limitations of the variable itself.

Edited February 9, 2012 by faldo

[BrewManNH]

$var[1][0] = String($var[1][0])

[faldo]

$var[1][0] = String($var[1][0])

That didn't seem to work...

To see what i mean, compare these two scripts:

$var = 11111111111111111111111111
MsgBox(0, "", $var )

$var = 1111111111111111111
MsgBox(0, "", $var )

It seems a variable can't contain a value higher than 9223372036854775807

Even if i do a $var[1][0] = String($var[1][0]) the result is a value in the variable, i need it to be a string.

Edited February 9, 2012 by faldo

[faldo]

I solved the issue with a workaround, i instructed the SQL-querry to convert the value to a string:

_SQL_GetTable2D(-1, "SELECT CAST(col1 AS char) FROM table ORDER BY id", $var, $iRows, $iColumns)

Cheers!

Edited February 9, 2012 by faldo