Search options (Page 3 of 25)

You really do not need to do an import for a new version of the software. You can do what I do. If a new version of your software requires a change to the structure of your database, you can create a small program which all it does is alter the structure of your end user's database. For example:

SqlExecute('ALTER TABLE company ADD COLUMN coPhone TEXT');

You can also create tables and even populate new tables through this program. Then when it comes time to distribute to your users, you send them the new version of your main program and in addition send them the small database upgrade program. Have your end users run the database upgrade program first. All this program does is change in place their database structure for the new version of your program. No import is necessary. When they run their new version of the program it will be accessing the new version of the database that is already populated.

If you use an install software for your users, you can have this database upgrade program automatically run during the install of your new main program. The user does not even know that it happened.

Optionally there is a PRAGMA instruction to check for the database version prior to the update. So that if the database is not the correct version, then you can take the appropriate steps to either update it or present an error message and not do the update.

wenchester21,
I put together the attached example for someone else on the forum in the past. It includes not only new action duplicates, but if the user also tries to change the info which would also cause a duplicate. See if it is workable for you.

Adam,
It was a little confusing to me. Your code is only retrieving values from one record in the SETTINGS table even though you have multiple records in there. So if you want to have multiple settings then you need to retrieve the corresponding values based on the selected row in your tablegrid. See attached for fix.

procedure Edit_function_button (Sender: TObject; Action: string);
begin

Form1.Table.dbsqlexecute('UPDATE Students SET Saff = "'+Form1.Edit1.Text+'",Fasl= "'+Form1.Edit2.Text+'",Name= "'+Form1.Name_txt.Text+'",Nationality= "'+Form1.Edit3.Text+'",Phone= "'+Form1.Phone_txt.Text+'",Gheyab= "'+Form1.Gheyab_txt.Text+'",Takheer= "'+Form1.Takheer_txt.Text+'",Health= "'+Form1.Health_txt.Text+'",Notes1= "'+Form1.Notes1_txt.Text+'",Notes2= "'+Form1.Notes2_txt.Text+'" WHERE id= "'+Form1.Edit4.Text+'" ;');

 Form1.Table.dbUpdate;

 end;

Form1.Table.dbsqlexecute is not the correct function. This is used to populate a tablegrid. You want to use SqlExecute('...'). However, you are putting in script which MVD will do for you without script.

Since you are relatively new to MVD, may I give you a little advice and it is exactly what I did in the beginning. I studied the examples/tutorials on this website until I understood how MVD works and what it does for you automatically with its Actions and form flow. I built very elementary projects to learn from. It seems like you are trying to go right into scripting without learning the basics of MVD. Believe me, you will have plenty of opportunities to interject scripting as you advance your projects. If I am wrong on this, my apology. But I just want to guide you in the right direction as a newbie.

kofa,
You cannot use SqlExecute to populate a tablegrid like you want. If you are not going to use the MVD built-in Search feature, then you either need a button with action of Sql Query, or dbSql script or dbFilter script. Take a look at the project I posted in this thread for a sample of dbFilter script.

kofa,
Although I do not agree with your design, I put in script to filter your tablegrid. I wasn't sure if you wanted OR logic or AND logic in your searches so each are independent filters. I did Saff combobox and Name edit field. In my opinion I think you are over scripting in your project, but I do not know what the big picture is for your application.

Why do you fill the search fields when you click on a row in the tablegrid?

It will just ignore the new fields.

Form1.mniFile.visible := false;
Form1.mniClose.visible := false;
Form1.mniOptions.visible := false;
Form1.mniSettings.visible := false;
Form1.mniReport.visible := false;
Form1.mniExportData.visible := false;
Form1.mniImportData.visible := false;
Form1.mniAbout.visible := false;

You can do this with a searchable combobox. Just turn on the searchable property and as you type into the combobox it will filter your selections.

webapplication4you,
Typically you do the same thing on subsequent forms. If you could attach your project we could take a look and see what is wrong.

I am a little concerned about that too. He has not participated on the forum for quite some time. Maybe it has to do with the pandemic or maybe he is working on a major release and does not have time to be on the forum. I don't know and wish he would communicate something on here to relieve some concerns as to the future of this product. I just hope he is alright.