Error Message: "bRun failed because Failure in the "CoordSysWizardMain" GX.NET Form (Input string was not in a correct format)", and Dapple is aborting

Problem/Symptom:
There are two related problems/symptoms here:

1) User trying to set any projection in a database, grid, or map, and continually get errors:

- "bRun failed because Failure in the "CoordSysWizardMain" GX.NET Form (Input string was not in a correct format)"

- "Unhandled exception has occurred in a component in your application. Details: System.FormatException: Input string was not in a correct format"

- Or any error with the text: "Input string was not in a correct format"

These error messages prevent the user from using the Coordinates Projection wizard.

2) User is continually getting a Dapple abort when trying to access it.

System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Double.Parse(String s, NumberStyles style, NumberFormatInfo info)
at Dapple.MainForm.loadCountryList()
at Dapple.MainForm..ctor(String strView, String strGeoTiff, String strGeotiffName, Boolean bGeotiffTmp, String strLastView, String strDatasetLink, ClientType eClientType, RemoteInterface oMRI, GeographicBoundingBox oAoi, String strAoiCoordinateSystem, String strMapFileName)
at Dapple.Program.Main(String[] args)

Thread count (including this one): 17

This abort prevents the user from using Dapple.

Environment:
This resolution applies to v7.0 of Oasis Montaj and Target, and v3.0 of Target for ArcGIS.

Resolution:
- Change the computer numerical settings to US English. You can change this setting via the Language Bar in the Windows Toolbars.

- You can also change the setting in the control panels. If you go into the Control Panels, Region and Language options, Customize, and change the decimal option (for example French) from a comma to a period.

- Once you've changed your settings, it is recommended that you re-start your computer.

Root Cause:
This is a bug that was introduced in v7.0. It has to do with the numerical language settings on your computer. More accurately, the problem lies with the existence of commas (instead of periods/decimals) in numerical values. This applies to computers that have their numerical preferences set in Canadian French, or some other languages (although we have only seen this problem with Canadian French numerical settings so far).

The programmers are working on fixing this bug for the next version.