Checkbox behind fields

[marcel2007]

I'm making a form with 20 fields. Each field is for a product feature. I use these fileds to mak several different outputs, like a product leaflet and a catalogue. Some of the features may be used for the leaflet, and some for the catalogue. To gain this, I want checkboxes behind every field. One for every output. Once checked, the feature must appear to the output and if unchecked, this feature will not appear on the output.

I've made the form and the outputs also, but I cannot get it to splite the features into different outputs. Can anyone give me a hint and help me out on this? Thanks!

[Tori Mitchell]

Well, you've stated the problem very well. How are you implementing this in your database design?

[Ender]

If you use a relational design for the list of features, it will be much easier to select and report on the outputs. In this case, you'd have a portal of Feature records. Depending on how flexible you need the selection and reporting, you can either use a separate field for each output (or a checkbox set in a single field), or instead make every Feature record about a specific output (one for "Modern Design" & "Product Sheet", one for "Modern Design" & "Catalog", etc.). The structure will depend somewhat on how you want the user interface to work.

[AudioFreak]

I think Ender was kinda headed the way I was thinking about this post. I just set up something here that sounded similiar. See Attached.

Might help, might not. Only took a few min to set it up.If anything maybe it will spark an idea.

HTH

Michael

Portal_Feature_Lookup.zip

Edited August 22, 2007 by Guest

[marcel2007]

Sorry,

from Holland and only understand simple English. Please try to explain more simple.

[marcel2007]

The problem is not the inplementation, but how to get FMP to give different outputs.

Feature 1 must show up on a product leaflet and in the catalogue, but not on the internet site.

So the programming should be:

If checkbox 1a is checked, then show contents of field 1 on product leaflet layout.

If checkbox 1b is checked, then show contents of field 1 on catalogue layout.

If checkbox 1c is checked, then show contents of field 1 on internet layout.

But I cannot get it to work. Anyone?

[comment]

Put the features in a related Features table, where each feature is a separate record.

To produce a catalog, go to the Features table, find the features that are marked for catalog, and sort them by their parent product. Put the common product info in a sub-summary part, and the individual features in the body part.

[marcel2007]

Thanks for your answer, but it's no option to give each feature a seperate record. Features belong to product. Each product is a seperate record.

Does anyone have an idea how to do it with the given structure of the fields:

[comment]

Features belong to product. Each product is a seperate record.

That's no reason not to have the features in a separate table, as RELATED records. On the contrary, that would be the recommended practice - even before considering your current problem of separate outputs.

[marcel2007]

Maybe you are right, but I do not want to have to sort things out. Current situation: Just one click, and FMP makes a product leaflet out of the features. It now uses all features.

So my question: I want to check (in a checkbox)each feature. When checked, the feature must be printed on the product leaflet. If not checked, the feature will not be printed. So today I select which features are printed on the leaflet.

When some user tomorrow comes and want to print the leaflet, he can by just clicking the print function. He doesn't have to select which features are printed, because I did that for him yesterday...

I hope you understand. Maybe someone can help me?

[LaRetta]

The problem is not the inplementation, but how to get FMP to give different outputs.

You keep missing the point, stately quite clearly from several top Developers. The implementation RULES the output; you can't have efficient output (printing or User interaction) without proper implementation (structure).

LaRetta

[marcel2007]

Maybe you are right, but saying only that, is not helping me. Please take a look at my former posts and try to help me out on this.

It's just a simple form with 20 fields. When I click on the button PRINT, a layout opens and all 20 values from the fileds are printed under each other. But I do not want that. I want to select which feature is going to be printed when the button PRINT is clicked. The selection must be made in advance and through checkboxes near the feature field.

[LaRetta]

take a look at my former posts and try to help me out on this.

Believe it or not, I always read an entire thread before I respond; as most of the others do as well. You say you want it split into different outputs but you (again) miss the point. You should NOT have 20 fields to begin with. Any time you have many 'like' fields (particularly 20), it indicates a problem and you will CONTINUALLY hit a wall when you try to work in this twisted method.

We know what you want. We undestand what you are trying to do ... heck, probably everyone here has attempted the same (when new). But again, I tell you that it can be done much simpler if you will listen to what is being said to you.

[comment]

I think you explained the problem quite clearly in the original post. As LaRetta says, the REAL problem is your data structure- the difficulty in getting the output you want is only a symptom.

[marcel2007]

Ok, mea culpa.

Maybe you can give an example of how to make it then. Just a little sample script.

I'm stuck here.

[comment]

Here is something I put together very quickly. There are scripts to print a single product sheet, multiple product sheets (from the found set in Products), and a catalog. I didn't do the Internet thing, because you didn't say how that works, but I guess it would be very similar to a catalog, except you would export instead of printing.

FeatureCatalog.fp7.zip