No problem, and what you may find useful is the program in this article:
https://community.progress.com/s/article/How-to-bind-a-bindingsource-to-a-datagridview-with-batching
If you look at the makeAttachQuery method in example_form.cls that shows a very good example of displaying only required...
I am not sure of the actual problem, is it you want a way of hiding columns at different stages or only having required columns in the DataGridView?
If hiding columns you can loop through each column and based on the criteria hide that way:
DEFINE VARIABLE oDataGridViewColumn AS...
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...
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"...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.