Forum Post: RE: ODBC Problems
Some thoughts: ODBC cannot cross 32/64-bit boundary. You say that you are trying to use an Access database but this error message seems specific to SQL Server. Why would that be happening?
View ArticleForum Post: Visual COBOL equivalent to C# "Using" statement?
Hello all, Is there a Visual COBOL equivalent to the C# "Using" statement? ... as shown In the following C# example, the "Using" statement (not the "Using" directive)... (as in the statement that says...
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
Hello, The equivalent of the C# "Using" statement in Visual COBOL would be $set ilusing Example: $set ilusing "System.Data" Regards,
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
No, as I pointed out in the above, I am looking for the equivalent of the Using statement , not the Using directive .
View ArticleForum Post: Native/Managed System
We are implementing a system that we are transitioning from Native to Managed. We already have the native code running in Visual Cobol. We have started replacing some native programs with managed...
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
Sorry about that! As you already know, "using" has always been a reserved word in Cobol, and I read from MSDN here that " The using statement ensures that Dispose is called even if an exception...
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
Below is an example: perform using cn as type SqlConnection = new SqlConnection(connectString) set cmd to cn::CreateCommand() set cmd::CommandText to...
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
@MF_Fano - OK, well, as to there being no exact equivalent to the C# "using" statement, that confirms my suspicion, and I guess I can see why (there is already a using reserved word in COBOL, used for...
View ArticleForum Post: translate C# WriteLine to Visual COBOL
The following C# console program, when translated to the following Visual COBOL equivalent, produces different results - apparently the tab (the \t escape sequence) is not recognized in the COBOL...
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
This perform is not a loop. It is the equivalent of the C# or VB using block.
View ArticleForum Post: RE: ODBC Problems
I'm using the 32 bit ODBC Data source admin. so do I need to use the 64 bit version? I have no Idea any more.
View ArticleForum Post: RE: Visual COBOL equivalent to C# "Using" statement?
So, there really IS an equivalent! I will work with the code you provided to prove it to myself. Thanks!
View ArticleForum Post: RE: C$OSLockInfo not works with MF format files
Hi mikmng, After checking into this, it appears that the wholock utility does not have the ability to identify the Process ID holding a given record. I'd like to refer this to our development group...
View ArticleForum Post: RE: DISPLAY WINDOW
To get this to work, in the runtime.cfg file you must add this line: SET preprocess=window1
View ArticleForum Post: Save Screen Section Questions...
Hi All, Trying to display a screen section with a Master table and then hide it, and then display a screen section with a Detail table. I understand you use call "CBL_SCR_SAVE" to save the screen....
View ArticleForum Post: Virtual 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 ArticleForum Post: RE: Virtual COBOL Personal Edition
Hi, I'm newbie, so I may not have the right answer. I believe it's Visual Cobol PE that you're considering using. It has 2 forms, the first based on Eclipse, the second base on Visual Studio....
View ArticleForum Post: RE: translate C# WriteLine to Visual COBOL
... also notice that Visual COBOL ignored / had no issue with the semicolon at the end of the statement...
View ArticleForum Post: missing 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 ArticleForum Post: 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...
View Article