Space Tool - Limited Number Fields

[Tim Harland]

Hi All,

We are starting to use the space tool regularly for our area scheduling however we are very restricted by the number of fields that do not behave like numbers and so can't be summed or included in formulas.

For instance the 'number of occupants' - we need to add up these fields for escape purposes. None of the user defined fields act as numbers either so we cant even fudge it (perhaps using the proposed area field but we need more than 1 manually entered number field)

It seems like none of the user data fields behave like numbers even those that you would expect like count fields.

Does anyone know if 2013 has rectified this, as we are updating soon?

Thanks

Tim

[Hippocode]

I doubt a newer version would change the type of parameters. A lot of data in most objects is passed as a string, even if it stands for a number.

The reason is , unless its a dimension you can't have a "REAL" value, thus strings are often used (and converted afterwards) to solve that.

If you are retrieving that data trough a dbrow into a worksheet, you could use "VALUE(RecordName.FieldName)" to make the string "7" into number 7.

Trough script it would be Str2Num(); and Num2Str();

If you don't have "enough" fields to save all of your custom data, you can add parameters yourself, but again bound to the above described. But for your numbering, you could easily add a field as an integer. These parameters should be visible in the object info palette but can't be used in the script of the object itself. For that you will need to code your own spaceobject..

Edited February 19, 2013 by hippothamus

[Tim Harland]

Perfect, thanks Hippo - the VALUE works perfectly

T