retrieving selected checkboxes

[MacSig]

Hi everyone.

I have a field called documents rendered as checkboxes (values are taken from a value list).

Now I need to perform some calculation (basically to set the value of an other field) according to the checked values (number and values themselves).

 

Which function should I use to get the list of checked values? For instance in the situation below:

[    ]  Book

[    ]  Magazine

 

[ X ]  Journal

[ X ]  Diary

[    ]  Paper

I wish to get  2 and to get Journal and Diary. 

 

 

Thanks.

 

 

[LaRetta]

Fields which have a value list as checkbox will return the result as a multiline (carriage return separated values) so if you look at that field without the checkbox attached, it would show:

 

Journal

Diary

 

To get the count of items in the field use:  ValueCount ( yourCheckboxField ).  If you might need to create reports on these results, i.e. counting how many Journals (and possibly showing them in the body) and then how many diaries ... or if you have other information to track about the journal or diary, it is best to use a middle 'join' table so that each selection is a record.  There is certainly nothing wrong with using checkboxes; it would depend upon the purpose and use of these values.

Ah.  And if you want to count how many Diary are in a record set, you have a more difficult task (or at least a more costly one) and is why I mentioned splitting them into records instead.

 

If you would like to know how to set up a join, let us know. :-)

Also, are you really still in version 9?

Edited September 16, 2014 by LaRetta

[MacSig]

Thanks LaRetta for your reply.

Yes I'm still on version 9 and I don't plan to update anytime soon.

I have to do simple stuff so I feel checkboxes are fine for now and I'm almost there

The only missing thing is the ability to allow user to input a value in a field according to the checked boxes. For instance I have a field called MagazineIssue and I want user may input values only if the Magazine box is checked.  Is this possible?


Thanks again. 

[Rick Whitelaw]

I have to ask. Why would you not consider upgrading to version 13?

[MacSig]

Because I totally don't like FM (but I'm forced to use it from time to time - hopefully always less) so I don't want to spend money on upgrading. 

[Lee Smith]

comment, I remove my post and your reply to it, as my post was inappropriate.

[comment]

LOL. There are days when I am not so crazy about Filemaker myself. I am sure you've had those too.

[Lee Smith]

Yeah, that’s true. Message to self "never, never, never reply to a topic without at lease 1 cup of coffee." 

[Mark Scott]

Fair enough, MacSig, that you don't like FM; I'm sure you have your reasons.  But, just to test your assumptions a bit here, have you considered that maybe the things you don't like involve features and capabilities that were not present a decade ago in version 9—archaeologic time by software standards—but that would help you solve your problems easily in a more up-to-date version?  Case in point…

 

For instance I have a field called MagazineIssue and I want user may input values only if the Magazine box is checked.  Is this possible?

 

It's not only possible, but is drop-dead simple using FileMaker 13's "Hide object when…" setting.

 

But, I vote for LaRetta's suggestion that often (usually) the best design for this sort of data is a 1:M relationship to a join table, where the fields for those document type-specific values (e.g., "MagazineIssue") would only show up in a portal row for the related "Magazine" record.

 

FileMaker is like other db platforms, in that good design helps solve problems (although is a bit more tolerant of poor design than many other db environments). 

 

Just some food for thought.

 

Mark

[LaRetta]

The only missing thing is the ability to allow user to input a value in a field according to the checked boxes. For instance I have a field called MagazineIssue and I want user may input values only if the Magazine box is checked.  Is this possible?

 

Hi MacSig,

 

My apology for not responding to your additional question!  I didn't receive the email and I am STILL not receiving emails on this thread and I should be.  Normally I would catch it because I read most every post here but I must have been too busy to read forums at that time. :-/

 

As Mark says, it would be easy to hide fields until the User clicks the checkbox appropriately, if using 13, because of Hide.  Back in version 9, you would need to use invisible tab panel, single broken portal or some other trick to hide/display certain fields when needed.  Honestly, I'm surprised that version 9 even runs on newer OS'.  You don't indicate what OS version you are running but I would bet good money that you are on a Mac. :-)

 

I too can understand frustrations with FileMaker.  However I must say that the current version has improved substantially.   I've actually forgotten what tools were available in version 9 but if you are still stuck on this issue, I would be happy to dust off my v9 and we can help you resolve it.

[Rick Whitelaw]

LaRetta,

If 9 doesn't run on a current OS, how would you open it? I believe I trashed FMP 9 due to this issue but I can't be sure. I've kept 10-13 though, or maybe 11-13 to be more accurate. I wanted to keep a version that would open FMP.7 files if necessary.

[LaRetta]

Because I kept a Windows system with XP on it.  :-)