link as submit in a form

is there a way to have just a link instead of a submit button that will POST
the form ????


thanks in advance

chris wrote:

is there a way to have just a link instead of a submit button that will
POST the form ????

http://tom.me.uk/scripting/submit.asp

--
David Dorward <http://dorward.me.uk/>

"chris" <someone (AT) here (DOT) com> wrote in news:3fe0935e$1 (AT) funnel (DOT) arach.net.au:

is there a way to have just a link instead of a submit button that
will POST the form ????

It can be done using scripting, but it's a bad idea unless there are some
aspects of your site that you aren't telling us about. In general, users
expect buttons to submit forms and links to take them to new pages.
Fundamental user-interface behavior should be as unsurprising as possible;
you need to have a *really* good reason to tinker with it.

Some things that may be unacceptable on the WWW may be at least marginally
acceptable in intranet applications, but you haven't told us what you're
trying to accomplish. I get the hunch that you've got an "XY problem" (you
want to accomplish goal X, and you've decided that implementation Y is the
way to accomplish it, but there may be a better way of achieving X).

ok what i am trying to do is link to another page and send information along
to that page by way of hidden fields, rather than use the
secondpage.php?info=blah etc

any other idea's would be greatly appreciated

"Eric Bohlman" <ebohlman (AT) earthlink (DOT) net> wrote

"chris" <someone (AT) here (DOT) com> wrote in news:3fe0935e$1 (AT) funnel (DOT) arach.net.au:

is there a way to have just a link instead of a submit button that
will POST the form ????

It can be done using scripting, but it's a bad idea unless there are some
aspects of your site that you aren't telling us about. In general, users
expect buttons to submit forms and links to take them to new pages.
Fundamental user-interface behavior should be as unsurprising as possible;
you need to have a *really* good reason to tinker with it.

Some things that may be unacceptable on the WWW may be at least marginally
acceptable in intranet applications, but you haven't told us what you're
trying to accomplish. I get the hunch that you've got an "XY problem"
(you
want to accomplish goal X, and you've decided that implementation Y is the
way to accomplish it, but there may be a better way of achieving X).

"chris" <someone (AT) here (DOT) com> wrote in news:3fe12ae0$1 (AT) funnel (DOT) arach.net.au:

ok what i am trying to do is link to another page and send information
along to that page by way of hidden fields, rather than use the
secondpage.php?info=blah etc

any other idea's would be greatly appreciated

Presumably, there's only a small number of possible combinations of the
values of those hidden fields. That means that each combination can be
associated with an encoding (small numbers work best) that can be decoded
by the server-side script that produces the linked resource. And that in
turn means that each page can include that encoding in the URL it links to.