[FX.php List] Re-That sinking feeling: FileMaker 12 & FX ?

[Steve Winter]

Malcolm

Which entirely validates my point… 

The grammar used by the PHP API does not display the bug, thus the PHP API does not have any issues and upgrades have (so far for me at least) been entirely painless. It's possible that this is just plain dumb good luck, or it's possible that because the API is a core component of the product both the API and the XML grammar which it relies upon have been more throughly tested than the alternative grammar.

Cheers
Steve

> The clues were given earlier in the thread:
> 
> Beverly Voth:
> 
>> Have you tried the grammar that is used by the FM API for PHP? fmresultset, rather than FMPXMLRESULT? You can't export with fmresultset, but you can make an XML web publishing request.
> 
> Troy Meyers:
>> FMRESULTSET also omits data for portals that have no related records, but since the data itself is wrapped with the field identity, this would not cause the misalignment of field/data problem
> 
> 
> Malcolm
> 
> 
> 
> On 11/05/2012, at 10:14 AM, Bruce Robertson wrote:
> 
>> That makes sense. But then how does that fit with the observation made by some that the bug isn't observed with the standard PHP API?
>> 
>> Bruce Robertson
>> 
>> On May 10, 2012, at 4:54 PM, Malcolm Fitzgerald wrote:
>> 
>>> That's false logic. Both libraries send XML queries to the server and get XML back. The problem is a verified bug. 
>>> 
>>> malcolm
>>> 
>>> On 11/05/2012, at 3:32 AM, Steve Winter wrote:
>>> 
>>>> Hi Steve
>>>> 
>>>> I would add to this, that it's also less likely to suffer from issues with upgrades - the problems that the thread was about do not appear to exist with sites built using the API. While it may well be an FM bug that's causing the issue, none-the-less I expect that bugs are less likely to end up in the API than elsewhere…
>>>> 
>>>> My 2p
>>>> Another Steve
>>>> 
>>>>> Hi Steve
>>>>> 
>>>>> The main reason I use the API is that, as a consultant, I feel that if one of my clients ever wanted/needed to have someone else work on a site I've developed, it'd be easier for them to find someone who knows the API than someone who knows FX.  I don't believe that there are any negatives in the API that outweigh that.  So as much as I may like FX, I feel using the API is probably in my clients' best interest.
>>>>> 
>>>>> Best,
>>>>> -Joel
>>>>> 
>>>>> 
>>>>> On May 10, 2012, at 6:11 AM, Steven Thoms wrote:
>>>>> 
>>>>>> I'm still a strong FX guy,
>>>>>> 
>>>>>> What advantages do you see in the API?
>>>>>> 
>>>>>> I see the speed, simplicity, extensibility, and flexibility of FX as major advantages.
>>>>>> 
>>>>>> Steve
>>>>>> 207 798-0171
>>>>>> 
>>>>>> On May 9, 2012, at 6:56 PM, Joel Shapiro wrote:
>>>>>> 
>>>>>>> FWIW: I tend to use the API most often on new projects.
>>>>>> 
>>>>>> _______________________________________________
>>>>>> 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
>>>> 
>>>> Steve Winter
>>>> +44 777 852 4776
>>>> steve at bluecrocodile.co.nz
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list

Steve Winter
+44 777 852 4776
steve at bluecrocodile.co.nz