> Yeah, but COBOL is not going to impress anyone. No one wants it. > How I can suggest that a company build their future around COBOL?
But your whole goal was to write COBOL, just using C# syntax. You're throwing out most of the benefits of the last 40 years of computer science. > inline SQL supported? I understand this to mean that you can set the text of a query in the code, rather than calling a stored proc. I know nothing about any .Net implementations of COBOL. But assuming that it's CLI compliant, you've got no worries at all in this respect. It's a function of ADO.Net, and yes, it's supported. There are some who disagree with my stance on SPs (i.e., they're required in all cases), but if you're working on my team, I wouldn't let you do your inline SQL, either. It's more maintenance headaches, it blurs the architectural lines, and it's difficult to avoid vulnerabilities to injection attacks. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
