bazzer747

Hi David,

That's interesting, I'll make a note of this when they go to 10.4. I'm always having issues with upgrading. I don't mind a complete uninstall/reinstall if the upgrade is a major one with most of the files having been changed, but a 10.3.2 to 10.3.3 seems a very minor one. Why they can't just do a replace of the files updated (like most other software vendors do) I don't know. Smacks of laziness to me.

Hi Vandrovnik,

After your post I wondered about the next error, assuming it was caused by my renaming the file. However, it wasn't (I took snapshots), it was for another file in a different plug-in. So I went back and tried the same again (renaming the file). And this time the install worked OK!

So your answer was correct and it was my 'assumptions' that stopped me figuring this out first time. Many thanks for spurring me on.

Hi

I did this (well, I renamed it) and GetIt gave me yet another error.

Hi

I have a plug-in (Konopka VCL) that shows it is being loaded at startup of Delphi (10.3.3), but which isn't working correctly. The GetIt package Manager doesn't show that this plug-in is installed so doesn't have an 'uninstall' option. It does have the 'install' option, but when I try this it fails when trying to copy files which are held by another process (presumably Delphi since it 'loaded' the plug-in at start - see attached screenshot).

So for some reason it's got itself in a catch 22 state! I can neither use the plug-in nor uninstall it nor re-install it. I imagine I can uninstall the whole of Delhi and start again, but I'm wondering if there is a way to tell Delphi NOT to load that plug-in? If I can do that then maybe GetIt will install the plug-in without an error.

Another option would be to run GetIT outside of Delphi, then it might work because Delphi would not be holding on to any files that would stop the copy process.

Any thoughts would be useful.

Yes. 10.3.1 is just as bad. Doesn't anybody in Embarcadero read these posts and think 'Ah, an issue that bugs our community, I'll get it fixed'? I guess not as it never does. Not the only thing that never seems to work in new releases. Like try 'Tutorials' and click 'See more Snippets'. A blank screen!

Hi,

Many thanks for all suggestions., I done a lot more thinking of my problems and come up with the following code:

procedure ConnectLiveTest( fdc: String );
var i: Integer;
begin
for i :=  0 to dm.ComponentCount -1 do
  if dm.Components[ i ] is TFDQuery then
  begin
    if fdc = 'Live' then
    TFDQuery( dm.Components[ i ]).Connection:= dm.fdcLive1
    else
    TFDQuery( dm.Components[ i ]).Connection:= dm.fdcTest1;

    TFDQuery( dm.Components[ i ]).Active    := True;
  end;
end;

This allows me to quickly switch between Test and Live MSSQL Server databases. And (whilst I'm still testing) appears to work OK.

FDSQL - sorry, shorthand! Meant FDConnection1.ExecSQL (see http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Executing_Commands_(FireDAC)).

Thanks for tips here, I'll certainly look into both (Good job Chrome can translate pages :-)).

In my application I have a Data Module which has 2 FD Connections (one for Test site one for Live site) and over 20 FDQueries for all the tables and views (I connect to MS SQL Servers). My application fails quite regularly with error saying cannot access a closed dataset, and I think it is because at some stage I've used ExecSQL to insert or update a record and this appears to change the query in the FDQ. Which means I'm having to re-specify the sql query in code several times throughout the application.

It seems to me that this isn't very good coding/design. I can't use the FDCExecSQL command as I'm flipping between the Test and Live connections, again I feel this isn't the right way to do this.

If anybody can suggest a better way to manage my connectivity to avoid having to re-specify queries I would be very grateful.