Hello,

I am trying to understand how to use a checkbox field in a portal to make a selection. Here are the details:

Music:

- Music ID

- Type (checkbox with defined value list)

- Song Title

Themes

- Theme ID

- Music Type (drop down with same value list as Music:Type)

ThemeMusic

- Music ID

- Theme ID

In Themes I have a portal (ThemeMusic) used to select which songs to use. I can get the portal to do this fine, but I want to limit the list of songs available to those that have been checked the same as the chosen Music Type.

I know how to limit the records in the portal field if the original field (Music:Type in this case) can only have one selection, but needing the option for multiple choices is giving me problems.

If you know of any topics that already solve this (I didn't find any) please let me know.

Thanks.

I'm not one of the pros but since you are unanswered at this stage I'll have a look at it if you want to post your file. I have used checkbox sets in portals a few times.

Phil

here's a demo that might help.

307714.zip

Here is the file. The relationship diagram is a mess since I took an existing file and started removing uneeded tables from it.

Thanks.

Themes.fp7.zip

Thank you very much.

I think your example can work for me, but I really wanted to use a checkbox instead of portal to choose the Music Types. I also do not want to have to add the music from the available list, but I think I may be able to do it differently than you showed.

I will play with this some more.

Thanks again.

I want to thank you for the file. It was the key to figuring this out and I got it work with checkboxes. I can't say I exactly understand why it works, but I'm happy it does.

Thanks again.

I'm glad my demo helped. I'd be interested to see your solution. I didn't see a way to solve this without adding two join tables, MusicTypes and ThemeMusic.

I see that you like checkbox fields. I predict that you'll find them limiting, especially when trying to filter relationships, creating conditional value lists and when reporting. Consider join tables instead.

Here's my file. I basically copied what you did. I'm not sure if I need everything since I don't need to show all the possible songs and then add them, just show which ones match the type.

I only am using checkboxes for this because I have a library of 1000s of songs that need to be categorized and it seems as if it will be easier to make selections with checkboxes.

Thanks again.

Elements.fp7.zip

I'm not sure if I need everything since I don't need to show all the possible songs and then add them, just show which ones match the type.

My demo showed only songs that matched the Theme Type in the left portal. The right portal showed songs that had been added to the Theme.

I'll take a look at your file when I can. Bit busy this week.

Hi Barbara,

I hope you find this.

I previously applied your sample file to my databases, except I didn't plan on having the 'add' song capability. Now, I realize that I need it. I have tried to use your example but when I hit the 'add' button (a red circle in my case) I get the following error:

"This operation not possible because the target is not part of a related table."

Looking at your example, your table is not related either and the script works fine. I'm guessing I am missing something simple.

If you can take a look at my file I'd really, really appreciate it.

Thanks.

Is the last attachment your latest file?

The error message indicates a context issue.

I realized I uploaded the wrong file, but I've been having problems editing the post. I think there is an issue with the FMForums server.

I'll try to get the right one up tomorrow.

Thank you very much.

Elements.fp7.zip

Edited January 10, 200917 yr by Guest

Have you had a chance to look at this?

Are you available for outside projects? You can send me your rates, info etc.

Thanks.