How to disable save button?

Hello Adam,

Again an interesting question !

Here is what I would try if I were you :

Assuming you use the same form, and you use "hard coded new record and save" functions (no code on your part, just MVD doing it's job :

1- set edit fields and save button to "disabled"
2- just before the edit activates, enable them
3- just after the save action, disable them again

Disabling  AFTER the save action is easy, you just have to use the OnAfterClick property of the save button like :

procedure Form1_SaveButton_OnAfterClick (Sender: string);
begin
     Form1.Edit1.Enabled := False;
     Form1.Edit2.Enabled := False;
     // and so on for as many buttons as you have

     Form1.SaveButton.Enabled := False;
end;

Unfortunately, there is no OnBeforeClick property, so clicking on the "New record" button, can not enable the edit fields and button (that you previously had disabled by default).

What you could use is the OnMouseDown property. This will detect if a mouse button is clicked over the corresponding button, which is equivalent to an imaginary OnBeforeClick

procedure Form1_NewRecordButton_OnMouseDown (Sender: string; MouseLeft, MouseRight, MouseMiddle: boolean; Shift, Alt, Ctrl: boolean; X, Y: Integer);
begin
     Form1.Edit1.Enabled := True;
     Form1.Edit2.Enabled := True;
     // and so on for as many buttons as you have

     Form1.SaveButton.Enabled := True;     
end;

Try it for yourself and let me known if it worked, and don't forget to set your edit fields and save button to disabled by default.

Cheers

Mathias

Hello AD1408

I look at your project Inserting Records
I only consider form frmCustomers

When I click on Button Add NewCustomer, no entrie is possible, fields of Panel1 (Add New / Edit ...) remain disabled.
Because action of this button (NewRecord), calls frmCustomers.

But why clear all those fields since New Record Share (called by Add New Customer) automatically empty fields ?

On other side, if absolutely you want clear all fiels,instead of draining fields one by one, it is faster to use a loop that will read all these fields (of type TEdit) as : (see attachment

Otherwise why use the OnMouseDown procedure, it has no reason to be used here ?

Is it really usefull for your project to activate/deactivate button Save ?
It smells a bit the style effect.

I absolutely critical not how you think your project and encode (I've been there too during my early developer) but I quickly realized that the end user wants only one thing: that the program quickly leads to the essential.

As with every new project, I recommend pencil and paper to plan for (and note any improvements). But I have to be a dotard

I keep your project on the screen and continue to arrange for it runs perfectly.

JB

Hello AD1408

I better understand your project.

About my piece of code, you're right. There is a mistake.
I wrote the head by reading your save procedure.
I will resume at leisure by finding documentation.

About your fear to save duplicates, you could use this Dmitry's code to control  duplicates (se attachment)

I continue to work on your project and stay current

JB

Hello Derek, Adam, Math, Jean (heu no, Jean it's me !)

Derek, if you hide panel1 in Event OnAfterClidk for Button Save,
then no need to use procedure derekclearform.     

So I tested this :

1 - Behind event frmCustomer.OnShow :  write : frmCustomer.Panel1.Visible := False;

2 - Behind eventOnClick for button Add Customer : write : frmCustomer.Panel1.Visible := True;

3 - Behind event OnAfterClick for button Save : write : frmCustomer.Panel1.Visible := False;

As Button Add Customer calls action New Record, then when panel1 becomes visible, all fields of this panel will be empty because this action drains automatically all the fiels involved.

Therefore no need procedure DerekClearForm.

Are you OK with me ?

JB

Bonsoir JB, Adam, tout le monde!
The reason why I created the 'derekclearform' procedure is to stop a slight error happening.  For example:
1.  You click 'add a new record' but maybe get interrupted, so you press 'cancel' instead of 'save'. 
2.  The next time you 'click add a new record', the 2 'not null' edit fields (in this case, 'name' and 'surname') have not been cleared out. 
Admittedly, 'derekclearform' could have just specified the 2 'not null' fields but for completeness, I added the others as well.
Hope that makes sense.
Derek.

Hi Mathias,

Thanks a lot for the info....

I'm sure I'm doing something incorrectly, as your latest code didn't work at my end. When you have time, if possible, please apply
- disabling/enabling
- your duplicate checking to sample project and upload so that I can where are my mistakes.

Once again thank you for your kind help.

++++++++

One more question Mathias, if I may please..
I noticed you did some days calc example project.
How do I calculate present age of a person from date of birth. I couldn't write a script for it.