It seems it is locked to that color and although it is possible to change color not a natural thing to do:
https://stackoverflow.com/questions/778678/how-to-change-the-color-of-progressbar-in-c-sharp-net-3-5
It seems you have quite a few errors - could be in the include files - and not easy to see the problem as there appears to be missing datasets/function names and some code lines not being quite correct as similar to the GUID error in the () being used for GENERATE-UUID.
Maybe an idea to create...
I think this line is the problem:
ttContacts.ContactID = STRING(GUID(GENERATE-UUID())). /* Auto-generate ContactID */
If you change to this instead it compiles:
ttContacts.ContactID = STRING(GUID(GENERATE-UUID)). /* Auto-generate ContactID */
As Rob has posted the "the gateway" could be the cause, but if a Power BI issue then a bit of extra information.
When we added Power BI we encountered the exact same problems reported in this thread despite the number of connections/servers/brokers settings being what we thought was high...
That seems to suggest that something extra is happening that is clearing the rich text box. It could be the components are being reinitialized or the setrichTextBox1value method is being called again by something else which is passing a blank value. From what you have posted neither of these...
I am not sure of the actual problem as it appears you are showing the value in the rich text box:-
THIS-OBJECT:richTextBox1:Text = ipvalue.
Is the problem that you want to show all the previous values because currently it is only showing the previous value passed? If so, then does something...
Yes, as you can see from here, Thomas Wurl from Taste IT Consulting identified the problem and a fix and a case was opened but as yet still no official fix:
https://community.progress.com/s/question/0D74Q000008HoP7SAK/detail
Cecil, for a .NET solution your example is a good one as it shows it can be achieved with just a single line of code:
MESSAGE System.Globalization.CultureInfo:CurrentCulture:DateTimeFormat:GetMonthName(3) VIEW-AS ALERT-BOX INFORMATION.
I had previously been using something similar to this...
As far as I know the operation of temp-tables has not changed much/at all between versions 9 and 12, and the error you are getting is expected as the temp-table names are both the same. It may have been allowed in version 9 but not later versions.
Change the name for the new defined temp-table...
The only options I know of is as per this article:
https://community.progress.com/s/article/18493
Or something similar to this very old code snippet from many years ago:
DEFINE VARIABLE Font1 AS INTEGER INITIAL 1.
DEFINE VARIABLE Font2 AS INTEGER INITIAL 2.
DEFINE VARIABLE FontSelect AS...
Yes, this seems to be hidden deep as there is no indication of where it can be found. I do not know if what is posted here is any help:
https://stackoverflow.com/questions/44093544/how-to-install-windows-security-credentials-c-sharp-net-vs-2017
These things are never easy! So I am guessing the problem is that the CTRL-TAB is only applying to the master window and not others?
Is it possible in the master window you can get a handle to either the procedures, window or browse and if so set a CTRL-TAB specific trigger to the handle...
For a generic context you could iterate through the browse columns and check that way:
DEFINE VARIABLE brws-col-hdl AS HANDLE NO-UNDO.
DEFINE VARIABLE browse-hdl AS HANDLE NO-UNDO.
DEFINE VARIABLE i AS INTEGER NO-UNDO.
browse-hdl = BROWSE bwsItem:HANDLE.
DO i = 1 TO browse-hdl:NUM-COLUMNS...
Never used SELECT-NEXT-ROW so not sure the best solution. One idea is to check what has focus and if a cell then remove focus. A really rough example only but hopefully it gives some ideas:
ON CHOOSE OF cmdSelectNextRow IN FRAME fMain /* SELECT-NEXT-ROW */
DO:
DEF VAR rv AS LOGICAL NO-UNDO...
As Cecil posted, I think LONG is what you are looking for. I have rarely interacted with DLL's but I have seen examples like these:
PROCEDURE GetSysColor EXTERNAL "user32.dll":
DEFINE INPUT PARAMETER nIndex AS LONG.
DEFINE RETURN PARAMETER iWinColor AS HANDLE TO LONG.
END.
PROCEDURE...
I had something similar once, and like you it was only happening in different environments. I was not able to fathom out what was going on but it seemed some sort of repeat was going on and the close/exit was being applied twice. The second close was giving the error as the object did not...
Some of the components in mscom.ocx may already be naturally available as .NET components so you may not have to download or install anything.
In Progress Developer Studio create an ABL form and if you expand Toolbox-Microsoft Controls it will show all the components available - see attached...
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.