Stano

Put a picture of the form here at the time of design. Let us have some idea of what you are doing and probably how you are doing it. That way we're just guessing from the coffee.

Yes. But you are using a modified DBNavigator. See also the reply from JonRobertson.

Hm, I've opined that you should get rid of your DBNavigator altogether. You're supposed to make do with a standard one. Without the added buttons! Everything is linked to the record search in SearchBox. You chose the wrong methodology.

In that case, I recommend you to go to "help" and always check all the properties and methods of what you are interested in. You want to use. In this case, it's DataSet. After that, T(FD)Table and T(FD)Query are also included. They are its descendants. They inherit from it. This is a very best and recommended practice!

I personally wouldn't add buttons to a standard component. You need to use what is there. DBNavigator takes care of the button control automatically. You're supposed to use the DataSet.Locate() function in SearchBox.OnChange(?). Or another appropriate event - we don't know what you do where. I don't use SearchBox. I prefer ComboBox. That way you won't have to worry about anything. No additional buttons. Don't forget that you'll be using DBNavigator in multiple places. So don't break it.

Nobody knows what you're doing there. If you type a name in the search box, you also have to make sure that the record is set up correctly in the DataSet. Preferably using MyDataSet.Locate(PKeyName, PKeyValue, [loCaseInsensitive]); I'm assuming there's a bug there.

No, no. Things happen in the back that you ask him to do. But you have to make sure you update the data you see. That's what I was warning you about. You'd see that when using DB components. At least for learning purposes, put a DBGrid in there. You'll immediately see what's going on there.

GROUP is a reserved word. See "GROUP BY". That's why it doesn't work. Reserved words cannot be used in MetaData. You're supposed to have TDBEdit instead of TEdit. It seems to me that someone has written that to you here as well. Unless you didn't want to use DB components. I had such a period. I just had everything handled centrally using a class. If you're not going to have it that way, you'll have to take care of: retrieving data from the DB updating data e.g. changing a record storing the data in the DB It's a lot of extra unnecessary work. Plus a high probability of errors! One more addition. Use only capital letters of the English alphabet everywhere in the DB (MetaData). In the Delphi code, write the whole expression for Query.Sql.Text in uppercase as well. The reason for this is that some DBs require it. That's why I have set this as a default for myself. What if the DB changes? That's how I've seen it with all the pros as well.

In this case, put all affected components on the panel. Then set MyPanel.Enabled := False; Remark: For bulk setting of component properties on forms, I recommend to create a recursive function and deal with it there. be direct or create a list of components and work with it

FireDAC offers very many possibilities. I only know UniDAC for FB. The latter is very far beyond its capabilities. It needs to be well considered. It is a shame to lose them.

Inporting data from one DB to another has nothing to do with Delphi. Firebird (FB) runs on all Windows and many other platforms. I, as a layman, would not go into Interbase Lite. FB is always free for all states. That will not change in the future. I don't use any other DB. Importing data can be done in many ways. It depends on what you have available. One option is offered by Delphi itself. Something like BatchMove. It has been discussed here recently. You'll have to look it up. Given knowledge, I don't recommend it at the moment. I've done importing data from DBF as follows: I got the data in *.csv format I opened them in Excel and made the necessary adjustments field names corrections to the data. E.g. 1500 to 1500, dates, etc. Using DB Workbench, a commercial product, I performed the import

Here I dare to write that it is mandatory to use MyQurery.Open and not ExecSQL.

Do you happen to have leading characters in the table title?

Beware of unqualified statements involving always and never. Unless the advice is to never put pineapple on pizza. That one is just a fundamental law of nature. I agree. I'll keep an eye on it. I really am a layman. I was basing it on the PAL help. I have no other knowledge of it.

Personally, I think it would be easier to use Firebird. I don't even use another one. I also tried SQLite, but quickly dismissed it.

It doesn't matter what type of variable. The reason for this is the unnecessary repeated creation of the variable. We know that we only need to create it once.

Always before the loop.

I installed D12 and latest version of TMS VCL UI Pack. I don't have another version of Delhi. With automatic compilation. When compiling (component) I get an error: [dcc32 Fatal Error] TMSVCLUIPackPkgDXE14.dpk(176): E2225 Never-build package 'rtl' must be recompiled [dcc32 Fatal Error] EnJasotComponents.dpk(43): E2202 Required package 'TMSVCLUIPackPkgDXE14' not found in package TMSVCLUIPackPkgDXE14; {$IMPLICITBUILD OFF} I haven't come across that before. How can I fix it? Note: I've put this on TMS as well, but it's going to take a long time.

Bruno Fierens TMS Support November 27 When we moved everything to TMS Smart Setup, this will be addressed

I haven't seen it yet either. I only ever have a single version of Delphi. In the required section I had to replace these units: TMSVCLUIPackPkgDXE14, TMSVCLUIPackPkgExDXE14, dac280, ibdac280, That solved the problem. I don't use runtime packages. It's beyond my knowledge and needs. I've got three years' support. I don't plan to extend it anymore. I can handle a maximum of three upgrades

Ask here

From TMS: Delphi 12 uses package TMSVCLUIPackPkgDXE15.dproj So, if there are still dependencies in your project to TMSVCLUIPackPkgDXE14, you should replace this by TMSVCLUIPackPkgDXE15

So I have to wait for the D12 version?

I have: Winapi;System.Win;System;Data;Vcl;obsidium;Adv*;(BaseGrid);Virtual*;FireDAC;REST;Xml;fcx*;VclTee;jst*;Vst*;sub*;u* Result: uses Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, System.Generics.Collections, System.Generics.Defaults, System.DateUtils, Data.DB, Vcl.Graphics, Vcl.Controls, Vcl.Forms, Vcl.Dialogs, Vcl.ExtCtrls, Vcl.StdCtrls, advofficepager, AdvMemo, advglowbutton, advpanel, advstyleif, advappstyler, FireDAC.Comp.Client, FireDAC.Stan.Param, jstAdvPanel, BasalForm, Htmlabel;

I wanted to download the web installer (on line). I could not log in to my account. I have had problems with this in the past. My initial original email was deleted - the provider has gone defunct. So I created a new account with the old details. Except for the password. Now I log in, but no registered products show up. Thus I have nothing to download. Can anyone advise how to solve this? I have a license until 06.2027. It also says D12.