Die Holländer

Bit offtopic but.. Internally, we use OneNote for creating help files and application overviews, such as screenshots of forms with explanations. For us developers, who don’t have dedicated manual writers, OneNote is particularly useful because it can be shared across the network. This allows everyone to contribute additional information and screenshots to the pages. Each page is accessible via a unique GUID, enabling us to link a help menu item in Delphi directly to a specific OneNote page using ShellExecute. Over time, with continuous edits from users, these pages have become very helpful.

Maybe one of these LLM answers can give you some clue.. 1. DLL Entry Points and Initialization - **Check the DLL's initialization code:** When the DLL is loaded, it executes its initialization code (like `DllMain` in Windows). Make sure that the DLL does not have any dependencies that might be failing to initialize. If the DLL attempts to access global variables, specific configurations, or other resources that are not set up correctly due to the complex app's environment, it might lead to an access violation. - **Library Conflicts:** If the DLL relies on other libraries (DLLs or packages), check whether those are being loaded correctly in the context of the complex application. 2. Runtime Library Differences - **Delphi Runtime Compatibility:** The new Delphi 12 runtime libraries might not be fully compatible with how the complex app was built in Delphi 5. Make sure you’re using runtime libraries in your complex app that are compatible with both the environment it was built in and the DLL. - **Compiler Directives:** Check if your complex application has specific compiler directives that might affect memory management or other runtime settings. 3. Project Settings - **Memory Management Settings:** There have been changes in Delphi regarding memory management across versions. It’s possible that your complex Delphi 5 application is still using a legacy memory manager. If your DLL was compiled in Delphi XE, it may expect a different memory management model. Make sure that both applications (the complex one and the DLL) use the same memory manager settings. - **Undefined Symbols:** If your complex app has issues with undefined symbols or might not be properly linking certain required libraries, this could be causing the access violation when trying to load your DLL. 4. Versioning Issues - **Runtime Package Issues:** Ensure that the application and the DLL do not have mismatched version dependencies on any runtime packages. Sometimes migrating code from older Delphi versions to newer ones introduces package version discrepancies that can lead to ABI issues. - **Conditional Compilation Flags:** Make sure you check for any conditional compilation flags that might affect how the DLL behaves when loaded from the complex app versus the simpler test app. 5. Diagnostic/debugging strategies - **Debugging the DLL Load Process:** Since you cannot modify the DLL itself, consider using tools such as Dependency Walker or Process Monitor to check what resources the DLL is trying to access when loaded by the complex app. These tools can provide clues if it’s trying to access a file or resource that isn't available or accessible. - **Logging:** If possible, add logging to the DLL load process (if you can do it through some means, like modifying the loader or using external logging). This would help identify where the access violation occurs specifically. 6. Running Environment - **Environment Configuration:** Check if the environment from where you are launching the complex application is different from where you are launching your test application. Different environment variables or configurations could also impact loading behavior. 7. Compatibility Mode - **Run in Compatibility Mode:** Consider running the complex application in compatibility mode for an older version of Windows (like XP or 98) to check if there are any odd behavior issues related to the OS.

Since you wrote that a small D12 app can access the DLL, maybe you can start a new D12 project to get rid of the old project files (dpr, dproj, res, dsk, ..) and project settings. Then add your forms and units from the old application on it.

Make a small form with only the TImage and create it on top of the parent TDrawGrid form.

Maybe in your Delphi version is also a TActivityIndicator under Windows10 palette/components..

Put both components TImage and a TDrawGrid on separate panels.

Since you have a web app, consider a common technique used by Web, Android and iOS developers. You could simply embed a TWebBrowser component in your application and direct it to your web app's URL. This approach often goes unnoticed by users and management, providing a seamless experience while effectively integrating your web app into a native interface.

How to setup Firebird RDBMS on Windows in Azure/AWS/GCP

I use this setup that works great for my shopteam (POS system) VCL application -> FireDac -> Portal Azure -> Azure Database (link to Youtube Delphi example)-> MSSQL -> whitelist user IP -> Connect -> Concentrate on User/business problems instead of non RAD Web development issues (HTML/REST/JSON/Javascript) With only Azure subscription and MSSQL database (2GB: not sure..) I pay about 5 Euro per month.

Interesting will be how to handle files (save, loadfrom) and database access via FireDac.

Start making your own Excel object for your projects.. For example: constructor TExportExcel.Create; begin oXL := CreateOleObject('Excel.Application'); xlsClosed:=False; oXL.Visible := False; // Get a new workbook oWB := oXL.Workbooks.Add; oSheet := oWB.ActiveSheet; end; procedure TExportExcel.CloseExcel; begin oWB.Close; oXl.Quit; xlsClosed:=True; end; procedure TExportExcel.Open(aFileName: String); begin oXL.WorkBooks.Open(aFileName); oSheet := oXL.Workbooks[ExtractFileName(aFileName)].WorkSheets[1]; end; function TExportExcel.ColToText(aCol: integer): string; var d,m:integer; begin result:=''; if aCol<=0 then exit; aCol:=aCol-1; d:=aCol div 26; m:=aCol mod 26; result:=Char(ord('A')+m); if d>0 then begin result:=Char(ord('A')+d-1)+result; end; end; function TExportExcel.GetCell(aRow, aCol: integer): OLEVariant; begin result:=oSheet.Cells[aRow,aCol] end; procedure TExportExcel.SetCellBold(aRow, aCol: integer; const Value: OLEVariant); var oRng:OLEVariant; begin oSheet.Cells[aRow,aCol]:=Value; oRng:=oSheet.Range[CellToRange(aRow,aCol)]; oRng.Font.Bold:=True; end; procedure TExportExcel.SetCellValue(aRow, aCol: integer; const Value: OLEVariant); Begin oSheet.Cells[aRow,aCol].value := Value; End;

Link to otc.pl

Maybe they should be clear about the costs instead of you must contacting sales. I think this is a hurdle for many developers. (Normally you see this when the costs is high..) Just put some system senarios on the webpage with the costs needed. Even with (bit complex) MS-Azure subscription, for example, it is possible to do an overview of the costs.

or https://thinfinity-vui-v3-docs.cybelesoft.com/ It seems it delivers the whole environment needed.. Delphi Demo

No, but sadly enough, you are not able to figure out what is the cause of all these problems. You have an unstable IDE setup and because you use some incompatible components (without source..) you can not install a newer IDE, so you don't know if these problems are still in version 12 or in even in your version 11 (.3?) that I've used for one year without any of such problems you mentioned. There must be something you installed in you IDE that is causing these problems or maybe some hardware/connection problems. Install the latest Delphi version on a clean machine or in a virtual machine open some of the example projects and develop some extra features on it and see if you have all these problems you mentioned.

Yes, I think so too and I'm always amazed by people finding "tons of bugs" in Delphi while I have never real problems with Delphi. It's not because of simple projects. We developed our software for 20 years and use almost everything a modern application can do. Database, Printing, SFTP, COM, OLE word/excel, Webserver, XML, JSON, FMX, Owner drawing, Math calculations, Interfacing with other companies, etc... I only know that some had problems with the Delphi RIO version eating memory.: memory leaks with RIO

Sometimes my users get an SQL error maybe because the computer doesn't have the proper ODBC driver version installed. (Like "ODBC Driver 17 for SQL server") How in runTime can I ask FireDac to fetch this driver version used by the application? I have the FDConnection open.

The problem is to get this TFDPhysMSSQLDriverLink casting based on FDConnection.

I can't get the name like "ODBC Driver 17 for SQL server" but I see things like "17" by the statement under, so that will do.. Uses FireDAC.Phys.ODBCWrapper; SQLDriverName:=TODBCConnection(DatabaseConnectionObject.ADConnection.CliObj).DRIVER_NAME;//DRIVER_VER;// DRIVER_ODBC_VER;

Looks very nice but hard to find what the cost will be.. Ian?

To avoid hanging of the UI I use FireDac CmdExecMode: MyQuery.BeforeOpen:=FDQuery1BeforeOpen; MyQuery.AfterOpen:=FDQuery1AfterOpen; MyQuery.ResourceOptions.CmdExecMode:=amAsync Execute MyQuery; procedure FDQuery1BeforeOpen(DataSet: TDataSet); Begin fCurTime:=now; JvDesktopAlert2.HeaderText:='HeaderText'; JvDesktopAlert2.MessageText:='Fetching Data..'; JvDesktopAlert2.Execute(self.Handle); MyQuery.BeforeOpen := nil; End; procedure FDQuery1AfterOpen(DataSet: TDataSet); Begin //Reset MyQuery.ResourceOptions.CmdExecMode:=amBlocking; MyQuery.AfterOpen:=nil; Sleep(3000); JvDesktopAlert2.MessageText:='Execute Time: '+IntToStr(SecondsBetween(Now,fCurTime))+' Sec.'; JvDesktopAlert2.Close(False); //Extra Things.. End;

I've got thousands of large JSONS in the same format (like with intake data for many persons..) each with many objects and array's where the people wanted to do searching. I tried many Delphi JSON programming libraries but ended up by adding all the plain JSONS as records in the MSSQL database and wrote a SQL-View using the "OPENJSON" rowset function Now I can do: Select * FROM [View_JSON] where field=value Even better.. You can just do joins with "normal" tables.. Select * FROM [View_JSON_] left join myNormalTable on [View_JSON].field=myNormalTable.field=value and the speed.?

I like the native Delphi JSON Data Binding Wizard that creates objects for you by importing your JSON file.. neftali.clubdelphi json data binding wizard delphi 12