Trimble Business Center

Hi, 

very often I have CAD drawing in 2D , where would be great help to use Spot Elevation feature. But Elevation Text is with Comma decimal mark. TBC does not respect comma and it ignores numbers behind decimal mark.

Is there settings , what could be sovle that problem? 

TBC uses the comma when the language settings of your PC are set to a language / region that uses comma as the decimal separator (this is a Windows Regional Setting not a TBC Setting). When your Windows regional setting is correct, TBC should read the setting to interpret comma as a decimal point automatically.

Control Panel - Region - Change the Region to one that uses the comma as a decimal separator - e.g. Germany and then log out and log back in to Windows and then try TBC

I will verify with QA that this is the correct process this morning when the office opens - apologies I don't do this too often as I primarily support North America and this is never an issue here - however I know that this is the way that the comma / Decimal Point issue is handled.

Alan

I just tested this on my PC as follows

1. Control Panel
2. Select Region
3. Select Language Preferences
4. For Country or Region I selected Germany but retained my Language as English (Unted States)
5. Then close Control Panel
6. Run TBC
7. I created a piece of Text 123,123
8. I then ran the Spot command to convert Text to a point - I used Text Insertion Point as my point location
9. It created me a point at the insert point with Elevation 123.123

It seems like you can change this Windows Setting without a Restart and even without closing and reopening TBC

I also tried this in 5.00.02 and it appears to work even without changing the Region Settings - I got a point with the correct elevation from 123,123 - however because I did not Log Out and Back in again it could be that the Settings are not fully updated and continued to work.

Please also check that the Text itself has no elevation because that could throw off the Spot command if the Text is a numeric value but is placed at say elevation 245 it is possible that the point is computed at elevation 245 not the correct elevation as defined by the text (Use the Change Elevation Command to achieve this).

Alan