Customized error messages ?

[israelchris]

I want to customize the error messages, but I dont know how to do this, for example, into a form, the field key when is duplicate, the error messages say: values for this field must be unique: Id_product. I want to change the text by another one, specially in another language..

I hope somebody can help me.

Desktop application.

[Garry Flanigan]

Re: Customized error messages ?

I will be interested to see comments from others but I do not set unique at the table level (which causes the messages you mention when a duplicate is entered) and instead use code behind a save button to provide "friendly" messages .
By carefully controlling what a user can do in a form you can avoid all system messages.
I typically have "Add", "Change", "Delete", "Save", "Cancel" and
"Close" buttons on every form.
I also have control the appearance of buttons so that they appear "grayed out" when disabled. Also I have a label showing the mode that the form is in so users are aware of what is going on.

[Mike Wilson]

Re: Customized error messages ?

I"ll echo what Garry said. No Table level restrictions and code the evaluation of values. I have gone so far as using onle xdiaolgs for data entry/edits and evaluating the entry/edit values at the exit of the dialog. I have a whole group of messages that I have written into UDFs for this purpose. Here is a standard message box I might call.

FUNCTION dlg_msg_box2 AS V (input_msg as C, box_pos as C,open_time as n)
	
dim dlg_body as C
dim mdlg as C="ACTION MESSAGE"
vlen=len(alltrim(input_msg))+14
box_pos=word(box_pos,1,"-")+","+word(box_pos,2,"-")
input_msg=space(5)+input_msg

z1=<<%dg1%
{position=%dg1%

z2=<<%dg2%
}{background=yellow}{font=arial,10,b}{nocaption}
{lf};
{region}
{text=%dg2%

z3=<<%dg3%
,1input_msg}
{lf};
{endregion};
%dg3%

message_wave()
dlgF=z1+box_pos+z2+vlen+z3
'msgbox(dlgF)
ui_modeless_dlg_box(mdlg,dlgF)

xbasic_wait_for_idle()
sleep(open_time)
ui_modeless_dlg_close(mdlg)

END FUNCTION

[CALocklin]

Re: Customized error messages ?

Ah, the joy of computers - and databases. There are multiple way of doing just about everything.

I prefer to do most of my "field rule" checking (it's in quotes for a reason) at the table level so I don't have to do it for every form or have to worry that I did it differently in other forms. If I do it once correctly at the table level then I don't need to worry about it as I build each form. HOWEVER, if I want custom error messages then I don't use the built-in field rules.

In that case, my preferred method is to create my own CanSave Record script (or, more likely, a function call) that handles the "field rule" checking (that's why it's in quotes - it's often not a standard field rule) and provides my custom error messages.

Here's a simplistic example. (I really wouldn't restrict a table such that it required unique last names.)

tc = table.current()
tc.change_dtf = date()   [COLOR="Blue"]'This is the ONLY way a change date should be set. It should NEVER be a calc field - NEVER.[/COLOR]

IF tc.mode_get() = 2	'Enter mode.
     [COLOR="Blue"]'Since the table is in Enter mode, the lookup won't find the current record.[/COLOR]
     found_name = lookupc( "F", tc.last_name, "Last_name", "customer", "Last_Name" )
     IF found_name = new_last_name
          msg = "Duplicate last name" + crlf(2)
          msg = msg + "Please enter a different last name."
          ui_msg_box( "ERROR", msg, ui_attention_symbol )
          cancel()    [COLOR="blue"]'This is what keeps the record from saving.[/COLOR]
     END IF
END IF