I'm using the decimal point to make the math for creating and using the elements compact. But if I get rid of the decimal point by multiplying the list by 100, that'll put commands 7&8 out of commission & half of command 6.

But Axe doesn't allow anything >2^16-1.

Hmmm no i see the problem now.  The problem is unfortunately that Axe can only hold a max of 4.5 digits, and he is using all 14.  In that case, you would have to write your own routine to extract each digit individually, since it sounds like you aren't looking for the whole number anyway?

Ah, okay! Is this a carry over technique from TI-BASIC?

Oh, I see.

The problem is that when you store as a floating-point number, it's always stored in scientific notation (such as 3.2x10^1 as opposed to 32). So when you read from the number, you can't just read the first two digits and expect them to be the two digits before the decimal point. Sure, it would work for 3.2*10^1 (since the 3 and 2 are both in front of the decimal), but it fails for numbers below 10, since there's only one digit before the decimal (reading the first two digits of 9.0*10^0 gives you 90, not 9.0).

The exponent in this case is stored in the second byte of the floating point number ($82 in your example). Take that value and subtract $80, and that'll be the number of digits before the decimal point. So 3.2*10^1 would be stored as 00 82 32 00 00 00 00 00 00, while 9.0*10^0 would be stored as 00 81 90 00 00 00 00 00 00.

Hope this helps.

*Sigh* So how do I create a persisting Appvar?

Well, I need the ability to dymamically (that is such a cool word) lengthen and store to the Appvar whilst simultaneously making sure I don't scribble over anything.