Search options (Page 81 of 104)

Hi,
Perhaps you can do it a bit like this (see attached).
Derek.

Привет, Вертиби,
Если вы хотите использовать существующий флажок, это один из способов, которым вы могли бы попробовать, но есть и другие.
Опять же, сценарий просто упрощает работу конечного пользователя.
Надеюсь, это поможет,
Дерек.

Hi Sibprogsistem,
Это то, что тебе надо?
С Уважением,
Derek.

Hello Ahmadrazaullah,
Defining a field as 'text' doesn't prevent non alpha characters from being entered, it just means that numbers are also treated as text.
To prevent numbers from being entered DURING input, I would use a small script (please see attached).
You could also check for it when saving the form or when leaving the field - it really depends on what suits your application best.
Regards,
Derek.

Здравствуйте
Если две таблицы связаны более одного раза, вам нужно использовать вычисленные поля для отображения имен.
См. Пример (извините, но это на английском языке).
Дерек

Здравствуй,
Отвечает ли это на ваш первый вопрос?
Derek.

Hi Adam,
As I understand it, Dmitry's password strength app DOES evaluate all the criteria and not just length.  The length of any password is calculated and then it's strength is rated depending on whether instances of 'lowercase', 'uppercase', 'numbers' and 'special characters' occur within that password length.
For example, Dmitry takes a password that has a length of 9 and grades it 'very strong' if it has instances of 'lowercase', 'uppercase', 'numbers' and 'special characters', downgrades it to 'strong' if it doesn't use 'special characters, downgrades it further to 'medium' if it doesn't use 'numbers' etc etc.
In incorporating 'repeating characters' and 'patterns' (see attached), I've simply downgraded the rating by 2 levels, but it's arbitrary and you could set it to whatever level you decide on.
Derek.

Hi TC,
I was able to recreate your errors by adding new fields to the search, new columns to the tablegrid etc etc.
Then I started removing objects from the Form, one by one, and then tried (and succeeded) in recreating the error. 
When I removed the 'Edit Customer' button (which WAS Button4), everything started working as you'd expect.
But if I re-used Button4 for the Customer Edit, the problem returned.
So I simply added a completely new button (Button7) as the Edit Customer button and didn't encounter any further issues.
I vaguely remember having a similar problem ages ago after I'd made a load of changes to various objects on a form - but to be fair, it's very unusual and MVD is normally rock-solid on things like that.
Just to mention - I changed a few things on your form as part of testing (new search fields, new columns, incremental searches etc) so you'll probably want to change them back.  Should have put them back to how they were but I forgot - mea culpa - LOL!
Regards,
Derek.

Hello TCSPLINTERS, Hi EHW,
I wonder if you haven't created any 'events' that link an 'object' to procedures in your script (sorry for the terminology!).

1.  When you use scripting, you will see an 'events tab' for each object (a form, a button, a grid, a field, a label etc etc)
2.  In this example, if you want to create an 'on show' event for Form1, you need to click (3 times) on the specific event
3.  This will automatically created a 'Form1_OnShow' entry against that event and link you to the scripting screen.
In other words, you can't just go into the script and write some code without making sure that the link is in place, otherwise it will never run.
So, in your example, you'll need to create events for frmResults_OnShow and frmResults_dtTestDate_OnChange.
Please have a look at the attached screenshot which might make things clearer.
Hope that helps,
Derek.

Hi TCSplinters,
There are a couple of ways to do this but for me, the easiest is to use a calculated field.
Please see attached and let me know if anything's not clear.
Regards,
Derek

Hi Adam,
Rather than try to decide whether some passwords (in your example - '2222222') are weak, medium or strong), I'd possibly put some password rules in place that simply wouldn't allow it in the first place.
I've added a couple of examples in the script of Dmitry's Password Strength Meter program - one that doesn't allow for more than 2 repeating identical characters and one that doesn't allow for a basic pattern (ie 1212 or abab or xyxy).  You could add quite few extra ones depending on how far you want to take it.
However, I imagine it would be easy enough to take what I've done and translate it into the 'weak', 'medium' or 'strong' categories.
Hope this helps,
Derek.