Search results

Although I have not tried any of these it does appear that you can generate some kind of debug logs for Progress Developer Studio:- https://community.progress.com/s/article/P173077 https://community.progress.com/s/article/How-to-enable-the-Eclipse-debug-console-for-Developer-Studio...

The majority of the time you just require the .NET DLL to be added to assemblies.xml and nothing else. The only times I have experienced problems is if one of the following situations existed: The DLL was blocked so had to unblock. Access was required to another DLL and that DLL was missing...

It has been years since I used work-tables and cannot remember if they had this problem. The following rules for work-tables are listed here - one rule is finding with EXCLUSIVE-LOCK is disregarded - and is it possible the timer is resulting in the work-table being affected by applying one of...

I have never used this parameter so not sure but based on this it looks to be a standard start-up parameter: https://docs.progress.com/bundle/openedge-startup-and-parameter-reference/page/NET-Common-Language-Runtime-clrnetcore.html As per the attached try setting for the relevant project.

Just tried to test this and I am finding the exact same in that class browser is not listing anything. I wondered if this was one of a few .NET components that Progress cannot access but it appears to not be the case...

This is a coincidence as we have just encountered a problem in the "WriteData" procedure in smtpmail where the email server seemed to temporary glitch or connection was lost whilst a write was taking place which seemed to cause the whole lot getting stuck in a loop. Added the parts highlighted...

As Tom points out there is "if you are using PASOE, change parameters X, Y, and Z like so" guidance and different factors come into play. Although likely to be a bit old now this may provide a bit of useful information...

Converting an AppBuilder window into a .NET window is pretty straightforward as outlined here: https://community.progress.com/s/article/P145112 Other options: https://community.progress.com/s/article/000033191 https://community.progress.com/s/article/P190039 I have not worked with a .NET...

I am not sure, but I think the workings in Kb188557 do not work with static classes. One option to try/fix is to have your class as a singleton class instead and doing that you should find you can pickup any modifications without having to restart the whole session...

It may not possible in Progress as indicated here: https://community.progress.com/s/question/0D54Q00008gdkmwSAA/has-anyone-successfully-used-open-xml-sdk-from-abl

I have never used the DocumentFormat classes so if a problem with these do not know the answer, but if it is the case of your program not seeing the dll then hopefully a bit of information that may help. For deployment, if only running compiled programs then you do not actually require access...

Sorry, unfortunately not. I was hoping that could have been the solution but seems you have tried that and do not know of any other option.

There is the FGCOLOR code setting but that only affects the list and not the actual value/screen value: DEFINE VARIABLE COMBO-BOX-1 AS CHARACTER FORMAT "X(256)":U LABEL "Combo 1" VIEW-AS COMBO-BOX INNER-LINES 5 LIST-ITEMS "Item 1","Item 2","Item 3","Item 4","Item 5"...

As Simon points out, an unsupported feature and you need to use a commercial option. One option is a .NET solution and I outlined a very simple example here: https://www.progresstalk.com/threads/using-ocx-microsoft-richtextbox.141443/#post-406679

Rob, good point, and these sites confirm the efficiency: https://community.progress.com/s/article/P16635 https://community.progress.com/s/article/Running-a-prowin32-exe-as-a-background-process-causes-extremely-slow-login-times-in-Windows

I think you are missing is a second addition and also do not require the second formula to be part of the first addition. Try changing the first addition and then have a second addition similar to this: chworksheet:Range("A" + STRING(lcnt) + ":B" + STRING(lcnt)):FormatConditions:Add ( 2, ...

I am not sure, but I wonder if the problem is you have only added one FormatConditions, which explains why FormatConditions(1) is okay but not FormatConditions(2)?

Yes, the macro code helps to a degree but the actual solutions may have to be found online. To convert this code: Selection.FormatConditions.Add Type:=xlExpression, Formula1:="=""ah3 > 0""" Try this site: https://learn.microsoft.com/en-us/office/vba/api/excel.formatconditions.add Where you...

Does this help?: https://community.progress.com/s/article/P189645

Although version 9.1E you may find some help here: https://docs.progress.com/category/openedge-archives https://documentation.progress.com/output/ua/resources/OpenEdge/91D/oe-91d-pdfs.zip