[FX.php List] OK, this is driving me crazy... SOLVED

[Jonathan Schwartz]

Bob,

I expect we’ll be seeing a lot of each other. And I feel I already know your childhood sweetheart, Mary Abate.  I follow your Facebook page. ;-)

And we’ll have something else in common to talk about: https://www.facebook.com/MichaelSchwartzJazz?fref=ts

;-)

Jonathan Schwartz
jonathan at exit445.com



On Apr 25, 2015, at 9:40 AM, Bob Patin <bob at patin.com> wrote:

> Excellent plan; I'll give it a shot and let you know how it goes.
> 
> Since you're going to Las Vegas for Devcon, we MUST have a glass of wine one night, and I'll introduce you to my wife.
> 
> Best,
> 
> Bob
> 
>> On Apr 25, 2015, at 11:05 AM, Jonathan Schwartz <jonathan at exit445.com> wrote:
>> 
>> Bob,
>> 
>> It could be either the data in the value lists or the composer field.  Suggest you peruse the data and see what kind of stuff is in there.
>> 
>> How about this: Create one new record and put a known good value in the Composer field.
>> 
>> Change your query to search for that record.  If that works, you know that the query works for a known good value in the Composer field.
>> 
>> Then, add the value list fields to the layout one by one and see if/when it breaks.  If it breaks right away on the first value list, try another one.  The first one you try might be the culprit.  Keep in mind that multiple (or all) of the value lists might be bad.  Given the crap that end users will paste into a FileMaker field from MSWord or worse, I’m still betting on weird characters in either Composer or one or more of the value lists.
>> 
>> If all existing value lists fail, create a new value list and put it on the layout with Composer.
>> 
>> By this time, we have isolated all of the entities and should have an “Aha” moment of clarity.
>> 
>> The ultimate solution might be to apply a php function to the output of the data query to normalize data weirdness.
>> 
>> 
>> Jonathan Schwartz
>> jonathan at exit445.com
>> 
>> 
>> 
>> On Apr 25, 2015, at 8:43 AM, Bob Patin <bob at patin.com> wrote:
>> 
>>> But the value lists worked... it was another field ("composer") that did not until I created a new layout with only the COMPOSER field on it.
>>> 
>>> So if all the value lists loaded on one PHP page, but the query of the COMPOSER field failed, that would seem to indicate that the issue was with the data in the COMPOSER field.
>>> 
>>> Yet, when I created a new layout with just the COMPOSER field on it, it worked...
>>> 
>>> Or are you saying that even though all the above is true, the issue may still be in a value list? I've seen that before, but didn't look at it yet in this DB...
>>> 
>>> Bob Patin
>>> Longterm Solutions
>>> bob at longtermsolutions.com
>>> 615-333-6858
>>> FileMaker 9, 10, 11, 12 & 13 Certified Developer
>>> http://www.longtermsolutions.com
>>> -
>>> iChat: bobpatin at me.com
>>> Twitter: bobpatin
>>> —
>>> FileMaker Consulting 
>>> FileMaker Hosting for all versions of FileMaker
>>> PHP • Full email services • Free DNS hosting • Colocation • Consulting
>>> 
>>>> On Apr 25, 2015, at 10:33 AM, Jonathan Schwartz <jonathan at exit445.com> wrote:
>>>> 
>>>> My money is on non-standard characters hidden in one of the value lists.  FileMaker tolerates but PHP objects.
>>> 
>>> _______________________________________________
>>> FX.php_List mailing list
>>> FX.php_List at mail.iviking.org
>>> http://www.iviking.org/mailman/listinfo/fx.php_list
>> 
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list