Can you provide some more detail please?

What is the actual error that you are receiving and when do you receive it?

Are you referring to opening up a screenset using the Dialog System painter or when running your application containing an Activex control?

I recall that there were a couple bugs in the early releases of DS for VC that dealt with ActiveX controls but those were fixed in 2.2.

There is a known problem when trying to use DS with ActiveX controls in a Citrix environment because of how the PATH is searched for dependent files thru Citrix but this is out of our control.

If you can clarify the problem you are having I can provide you with better information.

Thanks.

I know we use extensive ActiveX controls using Dialog System and the GUI class library from Net Express 5.1 and Visual COBOL for Visual Studio 2013 without issues.

With Terminal servers our main executable is build as TSAWARE which deals with font and registry issues.

Neil  

the Problem is not with netexpress 5.x, the Problem is with visual Cobol 2.2. When editing the Screen with dswin.exe the application crashed

What error message do you receive when it crashes?

Does it crash when you add the ActiveX control to the screen by dragging it or when doing something else?

What ActiveX control are you using?

Does this happen for all ActiveX controls?

in netexpress 5.x i don't have any Problems. i am evaluating Visual Cobol 2.3 but i don't have the adding Tools oder compatiblity pack for this Version. But in Visual Cobol 2.2 i can load the screenset coming/created in Netexpress5.x, then when i doubleclick on the ActiveXObject dswin.exe crashed! i use mstgrid.ocx from http/.../www.mysofttool.com This can be download as testversion. Can i send you the file (module .gs)

i want to included this Visual Basic function:

object.Borders(EdgeConstants).LineStyle [=LineStyleConstants]

object.Borders(EdgeConstants).Color [=Value]

that i want to convert in Cobol to set borders in a grid cell in the grid! (as in a Excel cell)

Thanks for help

If you have a Visual COBOL serial number that is under maintenance, even if it is an evaluation copy then you should be able to download the Compatibility Addpack for 2.3 from the product updates site.

What is your product serial number?

Error in just-in-time-debugger from visual studio:

unbehandelte Ausnahme ("COBOL runtime: Fault detected") in DSWIN.exe[5488]. Microsoft visual Studio 2012

exceptions not ....

my Evaluation license are: 600000673206 and 600000647363, but i can't Register it. a email on supportline@microfocus.com have been send for any days, without help today. my Login Name is greiner

by adding the license number i become as answer "not found". i have done a documentation and send it to supportline. Also Register for the Newsletter is a Problem, the Internet site is not present!

On Windows 10, on some machines (probably 5%) we had to set the environment variable MFOLECL_NO_THREAD_INIT to Y in order to get dialog system for Visual COBOL 2013  to run that might also be worth a try.

i work on Windows 7 and not Windows 10 for information

greiner,

Serial number 600000673206 is for the VC Personal Edition product and does not provide any maintenance. Serial number 600000647363 is a 30-day evaluation serial number but it expired back in February. You will either have to request a new evaluation through our web site or contact your local Micro Focus Account Manager to set you up with a new evaluation copy perhaps longer than 30 days.

I will be happy to check if the problem you are experiencing still exists in the 2.3 product, if you send to me the screenset you are testing with as you previously suggested.

My email is chris.glazier@microfocus.com.

greiner,

I did not receive any files from you in my inbox and I looked to see if it went to junk mail and it wasn't there either.

From your post on the other thread it isn't clear to me whether or not you now have a valid serial number for a 30 day eval. If you do then you should download and test with the 2.3 compatibility addpack. If you do not have a valid eval serial number then you really need to get one.

Please let me know and I will contact our 1st line team that may be able to help you out.

hi Chris, i have installed the product vcvs2012_23.exe and compataddpack_231.msi. This was received by download link.

i have the same Problem by Dialog System screenset with integrated activex!!!

by compiling i have a new error Messages for a library containing only screensets:

C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\Microsoft.Common.targets(3390,5): error MSB3030: Datei "obj\\x86\\Debug\\adm-anb1" konnte nicht kopiert werden, da die Datei nicht gefunden wurde.

Translation:

File "obj\\x86\\Debug\\adm-anb1" can not be copied, the file was not found!

The product file should actually be vcvs2012_231.exe and not vcvs2012_23 as it should be for VC 2.3 update 1. I just installed this same version here into VS2012 Professional and it works fine using the MstGrd activex control and the screenset that you provided to me. I can double-click on the control, create a new one, open up the Programming Assistant, etc.

I would recommend that you open up a support incident with Customer Care if you continue to experience this problem as I can reproduce the behavior here.

The compiler error you are experiencing is most likely because you have the action of the screenset library set to build when it should be set to None and Copy to Output Folder.

the same problem with vcvs2012_231.exe!!!

same errors!

The version vcvs2012_23.exe will be given after registering for evaluate from microfocus!!! And all people is on holiday by microfocus and can't help for register the serial number. So is it no possible to open a case at supportline! the problem persist since weeks. Is this the future of MF VCobol?

My colleague Kim now has an open support incident for you and I am working with him to try to solve your problem. I cannot recreate the issue using the same product version in either VS2015 or VS2015 so there may be something in your environment that is different. Please continue to work this thru the incident and hopefully we can resolve it quickly.

Thanks.