RE: translate C# WriteLine to Visual COBOL
Strangely (and rather annoyingly) semicolon and comma have always been treated as white space by COBOL. I believe this was already the case in ANS 74 COBOL, and remains the case now. It would be nice...
View ArticleRE: translate C# WriteLine to Visual COBOL
As for the main point (support for /t etc.) it's true this is not supported by COBOL, and it would probably be difficult to introduce support at this stage because of compatibility issues.You can do...
View ArticleRE: missing End-Try swallows tail of program
Hi Austin1, you have to use the NOIMPLICITSCOPE directive in order to get warnings in this situation. I would tend to agree that this should be the default...
View ArticleRE: missing End-Try swallows tail of program
Remember that conditional statements in Cobol can also be terminated by a full stop which is the old standard. You can use “Display Exception1:Message.” The example has a full stop after goback so all...
View ArticleWindows 10 and Visual Studio 2015
When upgrading to Windows 10, is it necessary to get a revoke key?Will there be a Visual Cobol Version for Visual Studio 2015 available?
View ArticleVirtual COBOL Personal Edition
I am a former COBOL programmer and Systems Analyst looking to get back into coding. I want to sharpen my skills so I have signed up for the Personal Edition. I need to know what version I should...
View ArticleRE: Virtual COBOL Personal Edition
Hello,To add to peter-m's reply, you may want to consider to use Visual COBOL for Visual Studio 2012 instead of the one for Visual Studio 2010. Microsoft just dropped the support on Visual Studio...
View ArticleRE: missing End-Try swallows tail of program
OK, let me check that out.Can you give me the exact syntax of the $set directive for this "NOIMPLICITSCOPE"?Also, apparently (?) may need the exact syntax of the $set directive for the "WARNINGS(3)" or...
View ArticleRE: missing End-Try swallows tail of program
Should be just: $set NOIMPLICITSCOPE WARNINGS(2)
View Articlemissing End-Try swallows tail of program
It appears that in the following managed console program, if there is no run-time exception, "swallows" up the tail end of the program if the End-Try is missing. There appear to be no warnings, etc.,...
View ArticleCalling an exe
How do I call an exe for example notepad.exe or even exe done in NetExpress am with Visual COBOL 2.2, thank you.
View ArticleRE: Calling an exe
Hello,Each EXE is executed within its own process or run-unit, so it is not possible to call an EXE. Instead, you will need to create another run-unit from which you execute the EXE. You can find the...
View ArticleRE: ODBC Problems
Hello,I'm understanding here that you have a problem to connect to an Access database with Visual COBOL's OpenESQL. However, the error message seems to indicate you're trying to connect to SQL...
View ArticleRE: Calling an exe
I already knew this command, I found that did not work in VC, worked perfectly thank you
View ArticleRE: Calling an exe
I'm a bit confused with your reply. Are you saying that CBL_EXEC_RUN_UNIT "does not work" or "worked perfectly" in VC?I know there was an issue for a managed code to call CBL_EXEC_RUN_UNIT that runs a...
View ArticleRE: missing End-Try swallows tail of program
OK, thanks. That worked - it caused a blue squiggly line under the period on the goback statement, and hovering over this, it said "COBCH1227 : Scope terminator END-TRY generated implicitly" and on a...
View ArticleRE: Calling an exe
Olá Pita,Use a classe Process.method-id button1_Click final private.01 cExe type System.Diagnostics.Process.procedure division using by value sender as object e as type System.EventArgs. set cExe to...
View Article