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

Exceeding 255 Characters for One Value


Bob White

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

Recommended Posts

A value list that I am creating is a choice between several lengthy phrases being inserted in a formatted letter.. In ten years of using FMPro, I had never run into the fact that there is a 255 character limit for each value. And, since I was exceeding that number, the phases would truncate. I have found two tech bulletins (101491 and 102388) which advise that the workaround is "use a code value in the value list and set it to trigger a lookup into another file that contains the actual data to be entered."

My thought was that this meant to use the "use values from field" choice and have the appropriate text over in the chosen field. That doesn't work (or I'm not setting it up correctly!). Can one of you steer me in the right direction as regards what this tech bulleting is really saying? Thanx in advance, Bob.

Link to comment
Share on other sites

Do you mean the Define Fields>Options>AutoEnter>Looked-Up Value [specify Field] list? That is where I went based on your response. I added the text into a new field created on an already related database. Still not working. Did I understand correctly? Or? Thanx, Bob.

Link to comment
Share on other sites

OK,

put it this way

you have an file let's say List.fp5 with following structure:

List(listID. itemID, shortValue, longValue)

In your main file define an global text field gList and relationship listRel with file List.fp5

listRel::gList-->listID

Also define an value list myValueList ???

use values from field itemID form file List.fp5, display also shortValue, use only related values from relationship listRel.

Define another field in your main file: listItem

and create relationship itemRel with file List.fp5

itemRel::listItem-->itemID

Attach value list myValueList to this field on some of your layouts.

Now, access the longValue from file List.fp5 via relationship itemRel or if appropriate use lookup with the same relationship.

HTH

Dj

Link to comment
Share on other sites

  • 1 month later...

Djukic: I ended up doing something much simpler. On talking again with the users, I was able to determine the necessity (or absence) for this long paragraph was based upon another field that was already in the database. So, I just did an "Is Empty" test on that other field and put this paragraph in an "If" calculation field to make it appear when needed. Thank you for your help.

Link to comment
Share on other sites

This topic is 8158 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.