Greetings!

One of my value lists is supplying me with the following message when I attempt to make a new entry: "The length of the selected text (the application automatically highlights the entire list) cannot exceed 30000 characters;" consequently, I'm stumped.

Has anyone else experienced this? Is this a global parameter for all value lists (If so, it appears to me to be restrictive for a database program). Presuming I understand what happened here, is there some way to format the list to confirm and/or expand its parameters?

Regards, Scottish

You had me stumped there for a second but apparently the limit to a Customly Defined value list is 30,000 characters. Using a value list From a Field does not have the same limitation.

I am curious as to why you are entering values into the Custom Defined box rather than using a new table to hold each value?

'ello Enthusiast and thank you for taking time to reply to my post.

I don't believe I'm clear on your distinction between using the value list from a field versus a custom-defined list.

By using a value list from a field do I understand you correctly to mean to set the field up to auto enter (using value from the last record entered)?

My intention for setting it up the way I had...using a custom-defined list...was for precision. Although the database is still in its "infancy" stage at this point, I anticipate that precision would be critical as the database grows [shall I say "grows up,"] and therefore becomes more complex). :

Thank you! I'm Interested in your further thoughts and suggestions.

Scottish

Well I guess it depends on what you mean by precision? Two reasons I could see for wanting to use a custom defined list are:

1) It does not sort the Value List. Whatever order the values are entered is the way they will appear in the list.

2) adding seperators between values.

Take a look at the attached file. It has two tables the first being MyTable which has 1 Text field to hold whatever value you select in a Value List and a global field named valueList_Filter used to ...well filter a value list.

The second table named MyValueList holds the values for a Field Specified value list. If you notice on the main layout you can filter the FromField value list by selecting one of the Radio Button options. In the CustomValues list whatever order values were typed in is the order the values are returned in the list.

ValueList.zip

30,000 characters, at an average of let's say 6 characters per word, comes out as 5,000 words. Even at 4 words per value - that's still 1,250 values.

Restrictive? I am curious how do you plan to use a value list of this size:

A checkbox set? I don't think I could cram even half of that into a 19" screen using a 9 point sized font at maximum resolution.

A drop-down list of over 1,000 values? That's close to 16x screen height. To better illustrate: when you click on a drop-down field like that, the bottom value will be two floors down.

I appreciate that you included an attachment to illustrate your point, which I will experiment with on a smaller database that I just developed. Seems I might've, could'a, should'a set it up differently. Grrr!

It's so frustrating being green.

Will letcha know how it progresses...soon. Thanks so much!

Scottish[color:green][color:green]

Shifted option to select values from field, however here's the problem:

The list in question includes company names, of which it is imperative that the spelling be precise. I entered one company name improperly to test whether selecting fields would give me the results I need. When I shifted to use values from the field I found the value list to include the improperly spelled name in it. This is why I initially set the field up to draw data using custom values (whereas all references to company names would be precise). This is important.

Because the chance that I'm a blundering idiot (because I'm so green) is high, I ask for your patience (blushing).

Thank you for any further feedback or suggestions.

Scottish

Shifted option to select values from field, however here's the problem:

The list in question includes company names, of which it is imperative that the spelling be precise. I entered one company name improperly to test whether selecting fields would give me the results I need. When I shifted to use values from the field I found the value list to include the improperly spelled name in it. This is why I initially set the field up to draw data using custom values (whereas all references to company names would be precise). This is important.

Because the chance that I'm a blundering idiot (because I'm so green) is high, I ask for your patience (blushing).

Thank you for any further feedback or suggestions.

Scottish

I'm not sure I understand why you perceive a difference here? If you incorrectly type the company name in a Custom Value List the incorrect spelling would show in that value list also. What you put in is what you get out.

You should be getting your Company names for your value list directly from the file where the Company information is entered. This way you are getting a list from the source rather than copying the source which leaves room for user error. Whatever you need to do to insure the Company name is entered correctly in the Company file really has nothing to do with your value list. Your value list is going to return whatever has been entered for the Company name.

"If you incorrectly type the company name in a Custom Value List the incorrect spelling would show in that value list also. What you put in is what you get out."

Perhaps you over-looked the part where I described how I had entered a company name improperly INTENTIONALLY to test something.

After reviewing your reply one more time, it occurred to me that your perspective is secondary or after the fact (reference to a field that is ALREADY formatted). My perspective is the initial field; and I affirm (after doubting myself and reviewing my options over once again), that I indeed want the field formatted using a custom-defined value list...the purpose of which is precision (anticipating that, in the future, I will not be the only user).

Don't be a snot! :

There has been no sarcasm in any of my posts to you. People are here to help you, either you want the help or you dont.

We are left guessing at why you really need this custom Value List. Why not create a sample database, Zip the file and let us take a look at it?

G'mornin' Enthusiast...

I felt that your statement, "What you put in is what you get out" not only overlooked the point I was making (that I inputted data incorrectly intentionally to test field behavior after I formatted the field as you suggested) but also implied that I didn't get it. Your suggestion for me to define the value list to use values from a field also implied that I was referring to a field reference (whereas I was referring to how the primary field was set up). My trailing (light-hearted) comment "Don't be a snot" was my way of gently shedding light on your tone, which felt unjustifiably critical. Of course I realize that you (people) are trying to help; and I accept it graciously. THANK YOU!

I am unable to zip you a sample DB at this time.

How 'bout let's just start over by simply re-defining the initial question...

The question remains, "Can I expand text parameters in a custom-defined value list to exceed beyond 30,000 characters?" "...If so, how?," "...if not, "why?"

No, you can not go beyond the 30,000 characters because that is the physical limit of a Custom List as defined by Filemaker. The 2 advantages of a Custom Value list are no longer very useful long before 30,000 characters, in my opinion.

If you want to create a value list of the "primary field" simply specify the primary field as the field to use for the value list.

Got it. Thank you so much!

Scottish

BTW, Is it possible (or advisable) to incorporate the two? A value list generated from the field along with the custom value list already built?

Edited January 24, 200619 yr by Guest

Figured it out Enthusiast. Thanks again for your help.

Scottish