FYI,

Win7, Visual Studio 2013 Pro, version 12.0.40629.00 Update 5, .NET Framework version 4.5.51209, Visual COBOL version 2.2.

Here is a simple managed console app:

program-id. Program1 as "cblConTest1.Program1".

data division.
working-storage section.

01 WORK-STORAGE-GROUP-ITEM.
   05 TEST-1 PIC X(10) VALUE " ABCDEFGHI".
01 WorkString string.
01 CharArray1 character occurs any.
01 CharArray2 character occurs any.

procedure division.

   Set WorkString = TEST-1.
   Set CharArray1 = WorkString::ToArray.
   Set CharArray2 = TEST-1::ToArray.

    goback.

end program Program1.

The above builds/compiles with no errors or warnings.

When the last statement executes:

 1) in step-thru Debug mode, you get a "FatalExecutionEngineError was detected".

 2) in "Start Without Debugging" mode,  you get a Windows pop-up message that the app has stopped working and you are asked if you want to send more information about the problem [to Microsoft].

FYI,

Win7, Visual Studio 2013 Pro, version 12.0.40629.00 Update 5, .NET Framework version 4.5.51209, Visual COBOL version 2.2.

Here is a simple managed console app:

program-id. Program1 as "cblConTest1.Program1".

data division.
working-storage section.

01 WORK-STORAGE-GROUP-ITEM.
   05 TEST-1 PIC X(10) VALUE " ABCDEFGHI".
01 WorkString string.
01 CharArray1 character occurs any.
01 CharArray2 character occurs any.

procedure division.

   Set WorkString = TEST-1.
   Set CharArray1 = WorkString::ToArray.
   Set CharArray2 = TEST-1::ToArray.

    goback.

end program Program1.

The above builds/compiles with no errors or warnings.

When the last statement executes:

 1) in step-thru Debug mode, you get a "FatalExecutionEngineError was detected".

 2) in "Start Without Debugging" mode,  you get a Windows pop-up message that the app has stopped working and you are asked if you want to send more information about the problem [to Microsoft].