I am trying to process a form on the web, and break it up into several smaller forms, as the form is HUGE. Is there an easy way to get the web companion to exit the record and continue to the next form without using scripting, which obvsiously doesn't work on the web?

Any help would be appreciated. Thanks!

Why exit the record?

You can have unlimited forms calling each other in sequence as response page.

HTH

with recid and session variables you can store / edit pretty much anything you need to.

Hi, if I understand this all you need to do is break the form into a number of pages?

The action for the first page is a new record, with the second and subsequent pages as an edit page for that record. This also lets you deal with conditional responses as you can tailor the subsequent pages to reflect the first answers.

jeff

Jeff,

Can you elaborate on this? Perhaps I just do not have the right vocabulary. What you describe is exactly what I am looking for, subsequent pages with content based on the previous page. Thanks in advance!

That is why I asked you "Why exit the record?"

First form creates the record; next forms are just editing the same record.

What part is not clear?

I think this is just an issue of me not knowing the correct vocabulary here. I have to "exit" the record, because that is the script step to apply the changes to the form within FMP. I don't need to physically leave the form, but I can't figure out how to apply the information to the database to create the next form, based on the content entered in the previous. As it is now, I have a single button to apply changes, and another button to go to the next step. This is kind of confusing and I'd like to have just one button for submit and continue. Thanks!

I see. In form use -format to go to next page, where you'll display entered values and let user to fill more fields with data.

Like <INPUT type="hidden" name="-format" value="nextpage.htm">

HTH

I think the difference here is that I am using Instant Web Publishing, because its the back end of the application I am deploying that is important right now. When I revise the whole thing after initial implementation I am going to use CDML and Javascript on HTML pages to make the whole thing much smoother. I was just looking for a stop-gap solution to make it less confusing. Thanks!

Re: because that is the script step to apply the changes to the form within FMP.

The problem you are encountering may have to do with the limits on ScriptMaker in IWP, which allows only certain script events to perform.

Go straight to CDML, drop the use of ScriptMaker, and save yourself a lot of hassle.

Start by searching the CDML Forum for "CDML Reference database" and get it from the link. It will give you most of the syntax which you will need. The rest is covered in these forums.

Bon chance.

This is unfortunately what I figured. Thanks. Once I get the backend finsihed I'll begin work on v2.0 of the web interface. Thanks!

Hi, C! As the gang advises, you'll use -new > -edit > -edit > -edit... If you're new to CDML, though, note that I believe you must pair the -edit action with [FMP-CurrentRecord] or the -edit will not work. When I was a newbie, it took me a while to realize/find this.

Have fun!

--ST

Re: you must pair the -edit action with [FMP-CurrentRecord]

Just a minor change. It needs the [FMP-CurrentRecID]

All the best.

Garry

oops! thanx Garry! I am a little rusty! --ST