We have some Mapbasic software that updates character fields in existing mapinfo tables to decimal or float. The character fields are mostly numeric but some values are N/A to indicate not applicable which is more correct for us that 0.
This is working fine for values under 1,000 (note that the format has a comma in it) but for values greater than 1,000 it is treating the comma as a decimal point I think. Any numbers greater than this are altered to 1 2 etc WE are using commands as follows:
Alter Table "tmp_astext" ( modify LV Float )
Alter Table "tmp_astext" ( modify LV Decimal(16,4) )
Is there any way we can stop this behaviour without having to make the users remember to change the formats when creating the files initially (they are created from excel). I've tried using the command
Set Format Number "9,999.9"
in the Mapbasic window but it doesn't seem to help