Maxmimum length of -find request

[gumaction]

Does anyone know if there is a maximum length of a find request that can be used in FMPro - I have been having serious problems with the [FMP-linknext] etc tags - after clicking the third time an unexpected error occurs.

The only way around this is by right clicking (hold click on mac) and selecting open in new window - then they work fine.

Either that or, by taking out part of the url in the address bar -i.e. status=online& (a field in the database) it then also works to move through your results.

Very wierd all this.

any ideas.

Lewis.

[Anatoli]

Do you have the latest versions of FM and WC?

[gumaction]

Hi,

Yes I am running the latest versions of FM and WC.

I have tried many different things to stop the error - but it only seems to happen when the url in the address bar gets past a certain length.

I can't see any errors in the code, because the first two finds work perfectly, it is only when the FMP-linknext/ or likewise button is used for the second time.

I have tried to shorten the url by removing some tokens and using cookies instead (not ideal, I know)- this helps but, the url can still get too long.

Is there a setting in FMP for the maximum length of the URL?

Lewis.

[IdealData]

What error numbers are you getting ?

[gumaction]

Mark,

There are no error numbers - it just says

An unexpected error occurred: Unexpected end of file from server,

195.XXX.XXX.X

Click the Back button on your browser to return to the previous page

It is not like the normal FMP errors that have a code - the messafe above just comes up in a grey warning box with a red bar along the top.

I am running out of ideas fast - have you got any ideas?

Thanks for you interest.

Lewis

[IdealData]

Can you convert this cgi request into a form "post" as a test ?

[Keith M. Davie]

"...having serious problems with the [FMP-linknext] etc tags..."

cdml reference:

"The HTML between [FMP-LinkNext] and [/FMP-LinkNext] is replaced with a link to the next range of records based on the -Max and -Skip values used to create the current page.

"The link that is generated includes all the search and sort criteria that was used to generate the page this tag was on. The text between the two tags is not displayed if the last record in the found set is being displayed."

Since the link is generated by the tags, "taking out part of the url in the address bar" is altering that which was generated. If that is the case, you probably need to examine "...all the search and sort criteria that was used to generate the page this tag was on.". In other words, the code which you wrote to -find the entire set may have some sort of problem.

[gumaction]

Keith,

I appreciate what you're saying, but how come the -find is fine for the initial find request (records 1- 3) and also the second set of results (3 -6) but not the third, it seems that once you are on the second set of results it doesn't matter if you click next, prev last or first, the error appears.

I don't see why the -find would work and then stop working, even though;

"...all the search and sort criteria that was used to generate the page this tag was on." stays exactly the same.

thanks for your ideas

[gumaction]

Mark and the rest, thanks for your help so far, but I still haven't cracked it.

The first request is a 'post' from a form - it is the FMP-link buttons that convert it to a address line command (html anchor).

Having spoken to FileMaker UK - who were useless - the guy said he didn't know but FileMaker may only be able to handle a few search and sort variables (his advice was 'build the database and CDML again but in a more simple way'). I find it difficult to believe that you can not query a database with more than about three or four variables and subsequently sort your results. It can't be that mickey mouse that it can't handle a multiple field query.

The worst thing is that not even filemaker themselves know how their programme works!!

If anyone has anymore ideas help would be appreciated because my G4 is about to become amphibious and end up in the river!!!

[Keith M. Davie]

"I find it difficult to believe that you can not query a database with more than about three or four variables and subsequently sort your results."

Perhaps there is something about your syntax. What is the code of your initial -find action, your form?

[gumaction]

Keith,

The initial find is my form pasted below.

<form name="form[FMP-currentrecid]" action="FMPro" method="post">

<input type="hidden" name="-db" value="Media">

<input type="hidden" name="-lay" value="web">

<input type="hidden" name="-format" value="b_rsltsc.html">

<input type="hidden" name="-token.1" value="[FMP-currenttoken:1]"> // usually a short number

<input type="hidden" name="-token.3" value="[FMP-currenttoken:3]"> //usually a short number

<input type="hidden" name="-token.4" value="[FMP-currenttoken:4]"> // a single letter

<input type="hidden" name="model" value="=[FMP-field:make][FMP-field:model] [FMP-field:year]"> // a make, model and year of car - i.e. ford mustang 1966

<input type="hidden" name="-sortfield" value="misc">

<input type="hidden" name="-sortorder" value="ascending">

<input type="hidden" name="-sortfield" value="image current">

<input type="hidden" name="-sortorder" value="ascending">

<input type="hidden" name="status" value="online">

<input type="hidden" name="-max" value="3">

<input type="hidden" name="-find">

</form>

The currentrecid is used in the form name because it is a repeating form for each record and they need to be unique to be able to submit them individually.

the results page from the form above then has the [FMP-link] tags I was rattling on about previously, this then converts the form to the url query (-find) automatically.

if it is easier to demonstrate, send me an email and I will reply with the actual URL.

Which look something like this:

http://www.abcxxxcdef.com/vxn/FMPro?-db=media&-format=b%5frsltsc.html&-lay=web&-sortfield=misc&-sortfield=image%20current&model=Astra%20Convertible%20Bertone%20Edition%202002%20Edition%201&status=online&-max=3&-skip=12&-token.1=00071&-token.3=33613&-token.4=C&-find=

Thanks again for your help.

[The Bridge]

In reply to:

---

The currentrecid is used in the form name because it is a repeating form for each record and they need to be unique to be able to submit them individually.

---

I don't know if this is the cause of your troubles, but have you tried the form without this unique naming scheme? I have a similar set-up with one of my results pages, where the [FMP-Record]...[/FMP-Record] tags enclose an identical form populated by record information. The forms all have the same name; no conflict arises when any of them are submitted.

It's worth a shot.

[Keith M. Davie]

I'll look at this later this evening (AZ time). I've got a full afternoon ahead.

To start, however, I've removed the sort code and re-arranged it to look like this:

<form name="form[FMP-currentrecid]" action="FMPro" method="post">

<input type="hidden" name="-db" value="Media">

<input type="hidden" name="-lay" value="web">

<input type="hidden" name="-format" value="b_rsltsc.html">

<input type="hidden" name="-token.1" value="[FMP-currenttoken:1]">

<input type="hidden" name="-token.3" value="[FMP-currenttoken:3]">

<input type="hidden" name="-token.4" value="[FMP-currenttoken:4]">

<input type="hidden" name="model" value="=[FMP-field:make][FMP-field:model] [FMP-field:year]">

<input type="hidden" name="status" value="online">

<input type="hidden" name="-max" value="3">

<input type="hidden" name="-find"> </form>

trying to identify the fields in the actual -find. I'll take it from there in a while. But the second equal sign "...value="=[FMP-field:make]..." is troublesome.

[Keith M. Davie]

I am taken by the fact that this form seems completely hard-coded. The tokens have been previously defined and are being carried forward. Three fields are being placed into one field. Those three fields have been somehow given values (to know its a Ford and not a Chevy. etc.).

Essentially this is a -find action on two fields, model and status.

But wait. Is it possible for the field model (name=

[dmartens]

I've run into similar problems with extremely long URL's. Interesting thing is, they don't work when clicked in the browser window, but they do work if copied and pasted into the browser Address line. It turned out I had over 250 characters in those urls, a very complicated find, sort, etc, using related fields. I ended up having to shorten the names of some of my fields and relationships, and then it worked properly.

The problem wasn't a limitation in the web companion, rather a problem in the browsers. Both Netscape and IE had the same problem.

[gumaction]

The input name="model" and [fmp-field:model] couldn't cause a infinite loop because it is swapping databases using the relationship;

model::model = media::model

You're right in that essentially it is only based on a few -find criteria - model, misc and image current.

--

Is it likely that the use of the currentrecid is causing the problem?

[Keith M. Davie]

It may be the use of the currentrecid. Try without that if you can. Is the form named for JavaScript?

The other thought is to copy and compare the url's generated with the linknext and see if any changes of significance are occurring. Might help understand the problem. Might not. And if you are running your web.log check it also.

Another thing is to look at the db after the initial find and each linknext. You may have to do this several times since you probably need to look at the db using Modify Last Find to see what is being entered or what else might be occurring.