Hi Hajo,
what backend database are you using?
personally i'd create a table called parameters, with the upper and lower limits you require (so that this can easily be changed) and then use the before edit or before add functions to check this value against the values in your "parameters" table, if this is within the parameters then allow the record to be added or amended, if it fails then dissallow the edit/addition and popup a messagebox telling the user why the record update/addition was refused. this way should you need to you can also enter different parameters for different users/groups without having to re-code everything.
sort of like (and i know this isnt the correct syntax)
enter value X
if value x is between parameter.low and parameter.high
commit record
else
messagebox"please enter a value for X between parameter.low and parameter.high"
dissalow record
Just a thought but it may be what you need, anyone with any other ideas please feel free to jump in <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=21004&image=1&table=forumreplies' class='bbc_emoticon' alt=':)' />
regards
Jason
Hello,
I have a web appliance project where I want to restrict the user to enter whatsoever price but to enter prices within a certain range.
Now, citing ex PHPR help file, i.e. "Scale (applies to DECIMAL datatype in SQL Server, Oracle and MySQL only)" I can see the SCALE option, but how reads the exact field entry ???, e.g. if wanting the user to only be able to enter a decimal value between $200 and $215 ???
The help file does not provide any example code, hence these lines.
Thx 4 short reply. Best - Hajo