I would like to figure out how a user can login fill out some of the form and then save it and come back at a later time and fill out more of the form.... We have a form that is quite long and needs this kind of ability.... i have tried using the form query but i cant get it to post back to the same record it creates a new one each time.... Not sure the best way mto go about this but appreciate the help

thanks

The only way you could do this right now would be to split the form and table into sections. Let me give this some thought and I will get back to you.

Steve

Steve, I have a similar requirement where I need to update a specific record in a table.

Steve V

At this point Form Master can be used to Chain forms together.

1.      Create the first form and map it to a table. When this form is submitted a Session variable named “ExtForeignKey” which holds the Identity Insert value from the insert statement. Redirect this form to form #2

2.      Create a second form probably on a hidden page and map this to another table which has a Foreign Key constraint to the first table. In the second form use a Hidden Field and Auto Fill the value from the Session value from the first form and map this hidden field to the Foreign Key field in the second table.

3.      You can continue this for as many forms/tables as needed.

 

What you can’t do:

1.      The user cannot move back in the chain

2.      Can’t reenter a chained form in another session as the “ExtForeignKey” will be lost

Form Master is on its way to Work Flow but it is not there yet.

My client is being a bit picky. Can I put several forms on one page and have them step through the same way, just never leave the page?

I have sort of come to a conclusion that in order to save data and transfer it without a table that has a zillion columns, I am going to need to split the form up. But my client does not want several pages to the process. UGH! It was easier with a store...but he didn't want that either.

Mabye you should explain to your client that end users are comfortalbe with the "Store" workflow model and making them learn new tasks to accomplish what has become a standard on the internet is never a good idea.

I am trying to understand passing information from one form to another.

My initial form is where the customer would enter a name and address, then they have options. I want the options they choose to take them to a new form, but populate the name and address from the first form into that new form.

I was reading your instructions above, but I guess I just don't know enough yet. I also read about field queries, session queries, etc, on other posts...and getting quite confused and frustrated.

I am feeling extremely stupid at this point!!! On the second form, do I do an autofill using "session"? I was able to do an autofill using "member" to populate the first and last name...but that was real easy because it gave me a drop down list for the "Autofill from" field. But I have no idea how to populate the field using anything else.

If I use a session or url for field query, where do I get the paramater name from? Do I have to do a "Send Value By Options" selecting "Session", and set a Value Name in the first form in order to pull it into the second form? Will that generate the paramater name?

I am very new to using things like queries. I am a quick learner, and can usually figure things out on my own. But this really has me stumped and frustrated. Please explain it as if I do not have any previous knowledge of anything...as I am finding myself to be less knowledgable the further I go.

See the video linked below.

http://screencast.com/t/rBpgu1qfhv5Z

Copy and paste the URL because this Forum Module corrupts the URL

The _895 appened to the name of the session variable is the Module ID number of the source form. This can be seen in the URL when editing the form. BTW the varialbe name could be anything as long as they are the same in both the source and target form, and that session variable could be used in any form or any module which makes use of session variables.