B2019-082 – Set the PROMS executables to always use the U.S. date format (MM/DD/YYYY)

PROMS/ReferencedObjects/Exe/RefObj/CmpRpt/CmpRpt.cs

@@ -50,6 +50,10 @@ namespace CmpRpt
 			// Required for Windows Form Designer support
 			//
 			InitializeComponent();
+			// B2019-082 set the date format on the VEPROMS.exe thread to U.S. for i/o of a date string
+			//           this is to correct an issue for a UAE customer who could not open some procedures due to the desktop date setting using the "DD/MM/YYYY" instead of the "MM/DD/YYYY" format
+			//           NOTE: not doing the "Using System.Threading;" statement at beginning of file because it conflicts with the declaration of the "Timer" variable
+			System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
 
 		}
 

PROMS/ReferencedObjects/Exe/RefObj/ROEditor/ROEditor.cs

@@ -394,7 +394,11 @@ namespace ROEditor
 			//
 			// Required for Windows Form Designer support
 			//
-			InitializeComponent();	 
+			InitializeComponent();
+			// B2019-082 set the date format on the VEPROMS.exe thread to U.S. for i/o of a date string
+			//           this is to correct an issue for a UAE customer who could not open some procedures due to the desktop date setting using the "DD/MM/YYYY" instead of the "MM/DD/YYYY" format
+			//           NOTE: not doing the "Using System.Threading;" statement at beginning of file because it conflicts with the declaration of the "Timer" variable
+			System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
 
 			// The data path the was passed in.
 			DbConnectPath = PassedInPath;

PROMS/VEPROMS User Interface/frmVEPROMS.cs

@@ -178,6 +178,10 @@ namespace VEPROMS
 			MyParent = myParent;
 			MyDocVersion=myDocVersion;
 			InitializeComponent();
+			// B2019-082 set the date format on the VEPROMS.exe thread to U.S. for i/o of a date string
+			//           this is to correct an issue for a UAE customer who could not open some procedures due to the desktop date setting using the "DD/MM/YYYY" instead of the "MM/DD/YYYY" format
+			//           NOTE: not doing the "Using System.Threading;" statement at beginning of file because it conflicts with the declaration of the "Timer" variable
+			System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
 			displayRO.TabControl = tc; // B2019-043 this was being passed in as a parameter for DisplayRO which caused issues with the Visual Studio designer
 			SetupFolder(MyDocVersion.FolderID);
 			tc.MySessionInfo = MyParent.MySessionInfo;
@@ -259,6 +263,10 @@ namespace VEPROMS
 					VEPROMS.CSLA.Library.Database.ConnectionName = "VEPROMS_LOCAL";
 			}
 			InitializeComponent();
+			// B2019-082 set the date format on the VEPROMS.exe thread to U.S. for i/o of a date string
+			//           this is to correct an issue for a UAE customer who could not open some procedures due to the desktop date setting using the "DD/MM/YYYY" instead of the "MM/DD/YYYY" format
+			//           NOTE: not doing the "Using System.Threading;" statement at beginning of file because it conflicts with the declaration of the "Timer" variable
+			System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("en-US");
 			displayRO.TabControl = tc; // B2019-043 this was being passed in as a parameter for DisplayRO which caused issues with the Visual Studio designer
 			bottomProgBar.ValueChanged += new EventHandler(bottomProgBar_ValueChanged);