Search options (Page 13 of 25)

Dimitry,
I don't know if I hit on a bug or not for searchable combobox. Take a look at the attached sample. Click on the combobox and type a 1 into the field to filter the list without clicking on the down arrow of the combobox first. When you do this, the mouse cursor disappears.  If you click on the arrow to dropdown the list first and then start typing in the filter, the mouse cursor stays intact as it should. Can you look into why the mouse cursor disappears? Thank you.

Thank you Dimitry. Would it be asking too much to include your examples that you provided in the forum. It would help in understanding the syntax of the new functionality. Appreciate it.

Adam,
Here you go. On the selected invoice I checked to see if a row was selected and if not then it selects the first one. You may want to put in a message instead.

Adam,
One thing that I notice is in your MyScrollSUPPLIER procedure you are loading the tgMainProducts selectedrow. I think it should be tgMainSupplier selectedrow.

procedure MyScrollSUPPLIER;
begin
if Form1.PageControl1.ActivePageIndex = 1 then
   begin
   if Form1.tgMainSupplier.selectedrow < 0 then Form1.tgMainSupplier.selectedrow := 0;
      vrowid := Form1.tgMainProducts.selectedrow;          // This should be vrowid := Form1.tgMainSupplier.selectedrow;
      Form1.tgMainSupplier.selectedrow := vrowid;
      Form1.tgMainSupplier.setfocus;
   end;
end;

l

Wenchester21,
Yes, you're right. That's why I asked Adam what the purpose of exporting the entire database to a csv file. If it's for backup purposes, then the app needs to be changed to incorporate the id's in each table. Usually exporting to and importing from processes are built to interact with third party software and then it's typically only certain tables that are involved. I will update the app to include id's, which should take care of your foreign key error.

Adam,
I had a chance to look at your project. I'm curious as to what is the purpose for exporting the entire database into a single csv file.

I took a slightly different approach but still using some of the concepts which Mathias suggested. In the attached project I coded it in such a way that you do not need to manually put in SELECT or INSERT statements for all your tables. and fields. The script will automatically retrieve all tables and columns within each table and build a single csv file for exporting.

As far as for importing, I had to create header lines for each table in the export procedure in order to distinguish between tables when reading the single csv file during the import process.

I used  a different process for checking duplicates when importing. The import process will do an SQL SELECT to see if the record exists in the respective table. It checks all fields (except id) against the database table for equal values.

You should be able to transport the import-export scripts to any project. It's not dependent on specific table definitions. However, keep in mind that images really cannot be copied to csv files. Hope this helps.

Chances are that you forgot to include the new field in the list of fields to save in the SAVE ACTION of the form.

Mathias,
Did you try this:

SQLExecute('ATTACH DATABASE ''Old_Db.db'' as ''Old''');
    SQLExecute('PRAGMA Old.foreign_keys=OFF');

David,
See if the following works for you

procedure Form1_EditButton_OnClick (Sender: string; var Cancel: boolean);
begin
    If SqlExecute('Select Owner From yourTable where id = ' + Form1.TableGrid1.sqlValue) = 'System' then
       Begin
         ShowMessage('System record, cannot open');
         Cancel := True;
       End;
end;

Or you can also hide or disable the edit button when a row is selected that is a system owner record. The following is for a click on a row.

procedure Form1_TableGrid1_OnCellClick (Sender: string; ACol, ARow: Integer);
begin
    If SqlExecute('Select Owner From People where id = ' + Form1.TableGrid1.sqlValue) = 'System' then
      Form1.EditButton.Enabled := False else Form1.EditButton.Enabled := True;
end;

Adam,
If you are placing the SQL script inside an MVD project script, then you need to place the SQL scripts inside MVD SQLExecute commands.
SqlExecute('Create....');
SqlExecute('Insert.....');
SqlExecute('Drop......');
SqlExecute('Alter......');

Adam,
Yes you can use it for any memo field. In fact you can use it for any control in any form if you want. The values inside the brackets [ ] can be any value you want. I elected to use the ?form.control" name for easier readability. Whatever value you use just make sure that your font button OnClick procedure has the same value and the OnShow procedure for the control LoadFont has the same value.

There are usually more than one way to do things in MVD. I'm glad Dimitry shows other ways of doing things especially when it may not be obvious to some or hasn't been exposed previously in the forum.  It's always beneficial to me to see other ways.

As far as your lines inside memo fields, using a pixel based elastic line, as you put it, is not an option in memo fields in it's current state. When Dimitry introduces an RTF type memo fields, then maybe you'll be able to use this type of line. For now you're stuck with dashes or underscores.