[FX.php List] Choking on data returned

[Tim 'Webko' Booth]

I've also seen this when there are 'odd' characters in a text field (high
ASCII, or gremlins in BBEdit speak) - you could try exporting the lot into
a text file, run Zap Gremlins in BBEdit, and reimport and see how you go.

Cheers

Webko

On 29 September 2012 11:30, Denis Somar <dsomar at gmail.com> wrote:

> Debugging should be about breaking the tests into smaller chunks. Have you
> tried doing a loop and iterating an echo statement and seeing where it
> breaks there?
>
> Can you display 10 records, 20, 50, etc.?  See if you can return one
> record, the. Expand the search and see where it breaks
>
>
> On Sep 28, 2012, at 5:23 PM, Bob Patin <bob at patin.com> wrote:
>
> I was already using it for paginating, but it doesn't really matter what I
> set it to, it still fails...
>
> Here's something else I'm seeing now, as I work on this:
>
> I have a SEARCH function, and when I put in a date range (like
> 5/1/2012...6/1/2012), I return 129 records, and these too fail to display.
>
> So this makes me wonder if there are just too many fields in his database
> and it's choking FX.
>
> I have about 150 fields or so on his web layout (I didn't design this
> database...); my question is this:
>
> I assume that when I return data, the only fields that are returned are
> those on the web layout, is that right? Most of these fields are empty on
> almost every record, and the few that have data contain only a half-dozen
> characters at most.
>
> SO... having said that, what is choking this?
>
> Would an ampersand in a field cause it?
>
> Bob Patin
> Longterm Solutions LLC
> bob at longtermsolutions.com
> 615-333-6858
> http://www.longtermsolutions.com
> FileMaker 9, 10 & 11 Certified Developer
> Member of FileMaker Business Alliance and FileMaker TechNet
> --
> Twitter: bobpatin
> Google+: http://www.longtermsolutions.com/plus
> AIM: longterm1954
> iChat: bobpatin
> --
> Expert FileMaker Consulting
> FileMaker Hosting for all versions of FileMaker
>
> On Sep 28, 2012, at 12:13 PM, Jonathan Schwartz <jschwartz at exit445.com>
> wrote:
>
> Sorry.
>
> In fx.php, it's called FMSkipRecords($skipsize).
>
> *FMSkipRecords ($skipSize)
> *This function is used to specify which record in the found set should be
> the first returned to FX. FMSkipRecords() is optional.
> *>>** $skipSize* is the only parameter taken by FMSkipRecords(). By
> incrementing or decrementing this value, records in the found set could be
> paged through in groups whose size was specified with the*$groupSize* parameter
> in SetDBData(). For example:
> $skipSize = $skipSize + $groupSize;
> $InstanceName->FMSkipRecords($skipSize);
> This would increment the number of records skipped by the value stored in*
>  $groupSize*, and then pass that parameter to FX so that* $skipSize* records
> will be skipped and the next* $groupSize* number of records will be
> returned by the current query.
>
> Just add $request->FMSkipRecords(60);
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20121002/35deb7fc/attachment.html