Sorry, forgot to reply to your earlier suggestion Jason. Agree that it is no really necessary, but it can be difficult to convince people of that…
As for the compulsory pair, I though that would only ensure that there is some value in both fields - but what I need is to ensure that if A is «no», the B SHOULD be empty - and if a is «yes», it should NOT be empty. Can I do that with a compulsory pair?
This is sort of like designing a complicated apparatus for a really simple problem.
I sort of see the issue, but am not really sure if you mean a “true/false” data element as opposed to a yes/no. If you use “Yes only”, then the value will be non-null only when checked. If so, then the compulsory pair should work.
Regards,
Jason
···
On Mon, May 5, 2014 at 11:26 PM, Olav Poppe olav.poppe@me.com wrote:
Sorry, forgot to reply to your earlier suggestion Jason. Agree that it is no really necessary, but it can be difficult to convince people of that…
As for the compulsory pair, I though that would only ensure that there is some value in both fields - but what I need is to ensure that if A is «no», the B SHOULD be empty - and if a is «yes», it should NOT be empty. Can I do that with a compulsory pair?
Hello Olav
We had similar issue when we were implementing the Tracer Medicine Form in the Tz database and we came to resort on having a javascript file to check the “Yes” and “No” values selected by the users.
I have attached the tracer medicine form and the script for your reference but just to shade some light on how the form structure and how the script works.
When the form loads, all columns are disable except the Eligible column.
If User selected “NO” in the Eligible column the remaining column will remain disabled. If the User selects “YES” the the Available Column is enable. The same technique is applied to the available column and on the last column if user chooses the drug is missing for less than a week then the other options are also disabled limiting him to select multiple option for the same drug
This is sort of like designing a complicated apparatus for a really simple problem.
I sort of see the issue, but am not really sure if you mean a “true/false” data element as opposed to a yes/no. If you use “Yes only”, then the value will be non-null only when checked. If so, then the compulsory pair should work.
On Mon, May 5, 2014 at 11:26 PM, Olav Poppe olav.poppe@me.com wrote:
Sorry, forgot to reply to your earlier suggestion Jason. Agree that it is no really necessary, but it can be difficult to convince people of that…
As for the compulsory pair, I though that would only ensure that there is some value in both fields - but what I need is to ensure that if A is «no», the B SHOULD be empty - and if a is «yes», it should NOT be empty. Can I do that with a compulsory pair?
This is sort of like designing a complicated apparatus for a really simple problem.
I sort of see the issue, but am not really sure if you mean a “true/false” data element as opposed to a yes/no. If you use “Yes only”, then the value will be non-null only when checked. If so, then the compulsory pair should work.
On Mon, May 5, 2014 at 11:26 PM, Olav Poppe olav.poppe@me.com wrote:
Sorry, forgot to reply to your earlier suggestion Jason. Agree that it is no really necessary, but it can be difficult to convince people of that…
As for the compulsory pair, I though that would only ensure that there is some value in both fields - but what I need is to ensure that if A is «no», the B SHOULD be empty - and if a is «yes», it should NOT be empty. Can I do that with a compulsory pair?