[X-POST] Unknown Command error

[BronwynL]

Hi

Is there any way to obtain the actual command value

from an Unknown Command error?

I'm using javascript pretty extensively in this particular

project. It works perfectly in Netscape, but fails with an

error 4 in IE. The weird thing is that if I put an alert()

statement anywhere relevant in the js, it works fine in IE

too. As soon as I remove the alert() it fails again.

Note that it's not returning my -error.htm page, I get it

direct from FMP-IWPerr.js

TIA

--

Bronwyn L

[Addam]

Sounds like there's something missing in your JavaScript syntax. If you post it, I'm sure I'll be able to help you.

The problem might also be in the URL. Take a look at it when you get that error and make sure that you don't have more "//" in the beginning of your URL than needed. That can cause that error to appear.

If your using "[FMP-Link]" be sure to take out what is not needed. If you don't FMP will continue to build on that url until the server doesn't recognize what you are trying to do and return an error, eventhough you just did it a few minutes before.

[Garry Claridge]

Try adding the line:

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

to your form.

All the best.

Garry

[BronwynL]

Thanks, Gary

You may have put me on the right track with your response. There are two forms on the page: one creates a new record in the Search Criteria db to track failed searches, the second is more or less just for them to enter the search that actually gets built in javascript. I'll try adding a -find tag and trap the onSubmit()

[BronwynL]

Thanks Addam

I really don't think you want to wade through it, but FYI the string that my function returns is

fmpro?-db=Items&-lay=itemDetailsWeb&-error=errors.htm&-Op=contains&-format=results.htm&Name_Display=blah%20blah%20blah&-max=10&-sortField=&-lop=or&-find

I then load that with a window.location.href=

The sortField just caught my eye, but FMP is quite happy to receive the same query from NN with no problems. I think Garry might be on to something with the hidden input that I'll then have to trap with an onSubmit()

tks for your interest