Create a calculation field, result text unstored (storage options), type or paste or create the following calculation:
ValueListItems ( Get ( FileName ) ; "New Value List" )
ValueListItems is a design function.
Replace New Value List with the name of your value list and it must be in quotes. Put the field on a layout all by its lonesome and print it. Keep in mind that when you consolidate the value items you need to replace the bad data, you do a find and replace field contents, or copy and paste, etc. the actual data in that field. Regardless of how you do it make plenty of backups along the way. ;-)
Umm. sounds good - using below (FM 11), but not working.fileName - the name of an open (local or remote).valuelist - the name of a in the specified database file.
I tested it on FMP 10 before I answered, not really sure how far back this function goes, but it is in FMP 7.
The value list I used in my test was from a field in the table. I just tried it in a related table, but one that doesn't contain the field from which the value list is created and it works fine.
Field specs: Calculation, returns text, and storage is set to unstored, under indexing check the check box to NOT store the calculation. If in doubt replace get filename with the name of the file in quotes. The name of the value list must also be in quotes, check your spelling.
Here's how I'd do it:
- Show all and sort by the category field.
- Go to File > Export Records…
- Add the category field to the export order
- Check the category field in the Group By section
- Export the data into a FileMaker file (or Excel or whatever you want).
You should get all of the unique instances of each category value that you can print from.
You can also use this as a "scrub" table that you can create a relationship to for the purpose of reassigning values. Be careful when doing find & replace because partial matches on similar values can ruin your data!
Dave, thanks for the alternative thought. - and the reminder about hasty F+R It's happened....
Bumper, reviewed all as described and still no joy. tested several lists; tried list origin field name instead of list name; expanded number of repetitions, .... There is some quirk that will reveal itself I expect and I'll be back to report.
If you want to send me a sample mini-file of what you are doing, I'll send you my email address.
What repetitions? Where repetitions?
Design functions are very handy for "looking inside" your solution, particularly if you do not have FM Advanced.
F & R has got to be one of the main reasons for Custom Menus, strip it out and never let users know it exists.
Bumper, More details may spark something....
The Value List "Additional Keys" is created from a field <People::sksadditional>.
New Field - <ListAdditional> is calculated : ValueListItems ( Get ( FileName ) ; "Additional Keys" ) With allow replace, no storage etc.
<SksAdditional> has repeating fields. I tested the new field without and with a matching number. [i know why not to use repeting fields, but in this instance they are category and skills check lists essentially for resume search/sort. it works. ]
Tried <ListAdditional> in people table, and in a table I use for global fields, unrelated to anything.
Layout basic, single field, tried browse, list; report.
not sure what else to include. reminder I am using FM 11.
New Field should be an unstored field of type calculation--not a text field with an auto-entered calculation.
Ah Ha! as they say. I knew there was something simple I had misunderstood. Apologies to Bumper and thanks all for your patience. And Phil for backing me up step.