Search results

Unfortunately the three dll files are too large to attach but they were downloaded from here and all unblocked: https://www.nuget.org/packages/FreeSpire.XLS The assemblies.xml file is blocked from sending so have changed to text to show you how it looks. The start-up parameters for the...

Yes, version 4.0 of the dll: Really odd that you are not seeing any classes for it. What do get when you run this: DEFINE VARIABLE oAssembly AS System.Reflection.Assembly NO-UNDO. oAssembly = System.Reflection.Assembly:LoadFile("C:\PathToFile\Spire.XLS.dll"). MESSAGE oAssembly:FullName...

Progress 11.7. That screen is the Class Browser screen in Progress Developer Studio: Expand the relevant project - only available if you have created one - and Referenced Assemblies, right-click the component and select:

What you have done seems correct, and as per the first two attached images it should work okay. Where are you getting the NotInheritable information from? As you can see from the last three attached images Progress Developer Studio does not say they are NotInheritable and only seems to have...

Forgot to add, you may need to unblock the two dll files: https://knowledgebase.progress.com/articles/Knowledge/Unable-to-add-assembly-references-in-PDS-after-downloading-3rd-party-DLL-and-copying-it-into-the-project

If this is the message then it means your Progress session is not seeing/knows nothing of the relevant component: Try the following: Place Spire.License.dll and Spire.XLS.dll in the Progress/Project working directory - MESSAGE SESSION:TEMP-DIRECTORY VIEW-AS ALERT-BOX. As per this site -...

I have no experience with NotInheritable Classes so cannot answer that part, but the version of Spire.Xls found here works fine with Progress: https://www.nuget.org/packages/FreeSpire.XLS/10.10.0 When you say it does not work what error message are you getting?

Yes, DocxFactory was great for this. I think it is still being maintained but is now called AKIOMA.Docs and is probably now a paid for solution: https://akioma.de/en/products/docs

Does this help?: https://knowledgebase.progress.com/articles/Knowledge/How-to-trap-the-BACK-TAB-SHIFT-TAB-key-combination-in-an-ABL-Net-form

I am not sure if that is allowed. You may have to use ANY-KEY or ANY-PRINTABLE instead and check for the key pressed: ON ANY-PRINTABLE OF FRAME F-Main DO: IF KEYFUNCTION(LASTKEY) = ":" THEN MESSAGE "toto" VIEW-AS ALERT-BOX INFO BUTTONS OK. END.

Yes, you are pretty much right. You use Visual Designer in PDSOE to create the .NET form and add the controls: https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/pdsoe/visual-container-types.html...

This seems to be similar but as you are on version 10.2B07 it should be fixed: https://knowledgebase.progress.com/articles/Knowledge/Multipleerrors6491fromAppBuilderSectionEditor Could any of these apply?: https://knowledgebase.progress.com/articles/Knowledge/P105162...

Not as extensive as proper training but these offer a little bit that you may find useful: http://download.psdn.com/media/architect_video/OOABL/SampleClass1.htm http://download.psdn.com/media/architect_video/OOABL/SampleClass2.htm https://www.progress.com/video/abl-object-oriented-programming...

It does appear to be the case and your solution looks to be the option as this one is similar: https://www.codeproject.com/Articles/51879/Converting-RTF-to-HTML-in-VB-NET-the-Easy-Way Apart from specialist third party .NET solutions there does not appear to be a natural way to convert RTF to HTML.

Not really sure about converting as there does not appear to be a method for that: https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.clipboard?view=netcore-3.1 As HTML is actually text does using System.Windows.Forms.Clipboard:GetText instead work?: lcHTML =...

Does this work?: System.Windows.Forms.Clipboard:SetData(System.Windows.Forms.DataFormats:Rtf, rtfString). lcHTML = System.Windows.Forms.Clipboard:GetData(System.Windows.Forms.DataFormats:Html).

I have never used multi-threaded DLLs so cannot answer direct, but a couple of comments from others on linking to multi-threaded DLLs were: You may find this useful: https://community-archive.progress.com/forums/00019/36671.html

That is a good question as very doubtful many developers use it. Progress says this: I suppose it is still useful for customers to easily retrieve various bits of information themselves without having to wait for development to write the programs.

It has been a long time since I used Results so this may not be the best answer. Cringer, you could say Results is similar to the AppBuilder as it allows you to select tables and fields to report on. The command to run Results is something like: C:\Progress\OpenEdge11\bin\prowin32.exe -db...

Yes, a solution that is clever but probably belongs in the category of "Even though it is allowed it does not mean you should do it".