cmnanax.blogg.se

Rad studio 10.2 tokyo review
Rad studio 10.2 tokyo review













rad studio 10.2 tokyo review
  1. #RAD STUDIO 10.2 TOKYO REVIEW 64 BIT#
  2. #RAD STUDIO 10.2 TOKYO REVIEW CODE#

A good idea would be to doing a number of bitness tests in your 64-bit "main app" (to evaluate whether you should execute your 32 bit or 64 bit COM utility) and then to ship both 32 and 64 bit utilities with your application to clients, always. Even worse, your users could be using Office 365 "online only" which means that the API's aren't available through COM on the machine at all. If the OS is 64 bit (which it usually is these days) then MS Office could be 32 bit or 64 bit (it's often still 32 bit) and Delphi apps could be either as well and if your Delphi app's bitness doesn't match that of Office your automation might fail. You've now touched on a touchy subject in respect of "bitness". Thanks again for explaining the Excel approach with Delphi in a simple way and for the really good Delphi blog.ĭonald Klopper at 11:39 that's why I posted my ideas in the comments as well. Unfortunately I will not be able to apply the same solution with Delphi 7 because it does not have a 64-bit target, but I am happy to have solved the problem. So I tried to change the Delphi target, from WIN32 to WIN64, in Berlin version of the project and recompiled it, without changing anything and. Looking for "EOleSysError" online, I found that one of the possible causes is access to a 64 bit server (my Excel) with a 32 bit module (my Delphi application). I couldn't understand where the mistake was. "Įrror #2: "Access violation at address 006695C6 in module 'ExcelTest.exe'. OpenFileName := FileOpenDialog1.FileName Procedure TForm1.OpenExcelFileClick(Sender: TObject) ĭisplayName := 'Excel files (*.xlsx *.xls)' įileOpenDialog1.Title := 'Select file to open' Procedure OpenExcelFileClick(Sender: TObject) Vcl.Controls, Vcl.Forms, Vcl.Dialogs, Excel2010, Vcl.StdCtrls, Vcl.Grids Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,

#RAD STUDIO 10.2 TOKYO REVIEW CODE#

The code that I have written as the test is: The crash is at function TExcelApplication.GetDefaultInterface: _Application, at the first line: The crash occurs in Excel_TLB.pas, which I imported as Donald Klopper suggested. Has anyone else had this and been able to solve it?

rad studio 10.2 tokyo review

I get an exception class $C00000005 error with access violation at Oxoo62fd0b: read of address 0x000001bc when I use Workbooks.Open. I have been trying to read from Excel and used this information as the basis for a test program.















Rad studio 10.2 tokyo review