Superb. When added the "by value" declaration to the procedure division header in the native subprogram, it works correctly. After that I tried to remove the attribute System.Security.SuppressUnmanagedCodeSecurity and it still seems ok. Do you think that this attribute should be still used ? Thanky you very much.
Now I'll try the directive NOILNATIVE.
I do not think that you specify the attribute as it doesn't appear to be required in this context. I read that it can be a security risk so you should be careful when using it.
There is a list of compatible SQL Data types in the product docs here:
Data items with usage COMP are supported but only for integer fields not for decimal.
Yes, I read it too and if it's not necessary I won't use the attribute. The only reason for which I was ready to use it was just very special combination of creating various visual objects within the form.
Hello,
could anyone help me ? I need to create a window as a form in Visual COBOL .NET and then create a listview object into this form but from the listview class written in simple native code. So after creation of the form I need to call native code with the handle of the form and here's the problem. First time I use the form handle in the native code as a parameter in calling Windows API functions causes exception and the process is terminated. I was looking for the solution and I've found that perhaps something like SuppressUnmanagedCodeSecurity attribute must be specified in the calling managed code. But I don't know if I'm right and if I'm how to declare it. In the attachment file is dialog-box with the exception thrown by first calling Windows API with the form handle.
Thank you very very very much. For this moment it does work just the way I wanted. Thank you for your help.
WOO HOO! Worked perfectly. Thank You!!!
Could you help me? I'm a student taking COBOL and I downloaded the Microfocus Visual COBOL PE and installed it in Visual Studio 15 Professional. When I create a COBOL project I get a product activation menu that asks if I want to activate automatically or manually. I tried activating automatically and got a "MG0006: Unable to authorize the request." error. So I tried activating manually and sent an email containing some kind of encrypted string to the license request email address at Microfocus. A Few minutes later I got back an email saying, "Authorization Process Error. The following error occurred during the authorization process: MG0006: Unable to authorize the request. I tried rebooting, reinstalling both Visual Studio and Visual COBOL, and searched the knowledgebase for a solution. This is my dad's computer (he owns Visual Studio 2015) and I don't know what to do. Here's the encrypted string I sent in the email.
Lucius Michael Dark
please take me off whatever email list I am on. I posted one thread and promptly received my answer. So thank you for that.
now i get several emails a day from threads I am not associated with.
i have tried muting the thread several times, and am taken to a page saying the thread is muted
however I still receive constant emails.
Please remove me asap.
Hi Chris,
I believe I'm using the 32 bit ODBC connector on Windows 10. Your form has no option for that. What should I do?
Linden
Linden,
That would go under the Windows 10 column under x86-64 running Windows for Question 2 which asks about ODBC/Connector product.
Ah sorry being thick! 32-ODBC in 64-bit Windows environments. I've emailed you. Cheers, Linden
Hello,
Micro Focus is looking for some information from customers who use the MySQL database in conjunction with our OpenESQL technology available in Visual COBOL. In particular we are looking for which MySQL products and platforms are being used.
I have attached a brief 4 question survey to this post which provides a list of products, versions and available platforms. We ask if you could please download this survey and fill out the form and then return it to me via email to chris.glazier@microfocus.com.
If you are not currently using OpenESQL or Visual COBOL, we ask that you still complete the survey and then in the comment fields indicate which products and technologies that you are using with MySQL.
Your help with this is greatly appreciated.
Thanks.
The two-finger touchpad scrolling stops working maybe half the time in the Visual COBOL IDE. It's really annoying. I'm using the latest Visual Studio community edition and latest Visual COBOL. Is this an MF problem or Microsoft?
Thanks,
Linden
Hi Ekstrand,
This should be resolved now. Could you please try and confirm?
Thanks,
Raquel
Hi. When you are logged in here, if you go to the header, you'll see "Notifications" as a link there. If you open that, you'll see an EMAIL tab. Go there and you can manage your email notifications. Let us know if that doesn't allow you to do manage your notifications like you want.
"set ilpinvoke" was working for VC 2.3.1 but we just installed 2.3.2 and I now get this compile error:
"ILPINVOKE invalid or not allowed here".
So I removed the ilpinvoke set statements and added "set noilnative" and tried using a procedure pointer
to load kernel32.dll. I also added a project reference to it in SysWOW64. I'm now getting this exception when setting the procedure pointer:
System.BadImageFormatException
Could not load file or assembly 'file:///S:\V63\AWCBL\DEBUG\kernel32.dll' or one of its dependencies. The module was expected to contain an assembly manifest.
Even though I get an exception, the WINAPI calls work but I get a run time error when exiting our application:
"MgLoad has stopped working". MgLoad is the managed driver for our application and is the first program called.
I would like to get the "set ilpinvoke" statement working again, like it did for VC 2.3.1.
I followed the instructions from this link:
http://community.microfocus.com/microfocus/cobol/visual_cobol/f/18/t/11460.aspx
I tried setting a procedure-pointer to the Windows libraries in order to load them but I get error 173 when executing the set procedure pointer statements.
For example: set pp to entry "kernel32.dll".
I had to set up project references to the libraries in my SysWOW64 folder. Does anyone know why setting a procedure-pointer isn't working?
This happens even if I include SywWOW64 in the path.
Hi Phil,
Please open up a support incident for this as ilpinvoke works fine for me here in 2.3 U2. It sounds as if your path has been corrupted or perhaps you inadvertently changed your project type from x86 to x64 or anyCPU?
Thanks.
Can you please clarify what you mean by managed console application? Are you referring to a managed console application compiled as an .EXE or as a .DLL? Are you referring to a managed procedural program instead of a class?