Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Old Data shows in fields wrecking my Value List


This topic is 5139 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have updated a data base I created, but my old records do not show the current information needed to take advantage of my implemented Value list. To make the value list work I needed to combine some fields and changed the combinations along the way while I was refining what I wanted (this combined field is what is not updating in the old records). All new records are fine but the old ones have this one field still showing the old original gathered information. Is there a way I can update the old information so all records are using the needed current information for my value list?

Thanks in advance,

Posted

Hello and welcome to the forum.

Your description is not detailed enough. Can you tell us the definition of the value list? Give an example of what is in an "old" record, and what you'd expect in an update.

Posted (edited)

Changing a value list does not change the existing data. You will have to do a find for each of the old values and use replace field contents to change the old value to whatever you would like the new value to be in those records.

Edited by Guest
Posted

That is a common problem with the FileMaker implementation of value lists. It is important to understand how they work. An easy way to do that is to create a copy of the field while in layout mode, but set the copy to show as a standard text field. Then you can see everything that's inside it.

Another very useful thing to do is go into find mode, click into this copy of the field and do "Insert from index" (command-I)

This will reveal to you all the values that are actually stored in the field.

You can also do this with any field. Sometimes it's frightening to try this on any field, such as the "Last Name" field, and find phone numbers, cities, all kinds of things that users have mistakenly entered.

Posted

Whenever possible, use a table to hold your values. Include (as always) a unique ID in this table and then another field to hold the value. Base your value lists on this ID and display the value as second field.

In this way, when you change the value in your value list, your data throughout your table will inherit the new value without need of searching and replacing through your records.

  • 3 weeks later...
Posted

Thank you everyone for the answers. It appears that it was only taking the additional new data for new entries. Old data stayed as is without the additional fields incorporated into them on the value list.

This topic is 5139 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.