Forums

Save and get data in a multi page form

Pietro7 26 May, 2014
Hi,

I have a multipage form, and I would like to add a button on each page which will save the already filled out questions. So when the user logs off for a while and than logs on again he will start from the page where he saved the form. Could you please help me with this problem?

Thank you very much

I know I should somehow store the data by pushing the button into a database, and when the user logs in again to retrieve the data by the id
GreyHead 27 May, 2014
1 Likes
Hi Petro7,

Add a submit button to your form, use a DB Save action to save the results so far. I'd do this with any multi-page form.

Re-starting is a little tricker. You need to identify the user, get the saved form data with a DB Read action, then redirect to the appropriate form page.

I think I would use a 'status' column in the database record to record the last page saved; that would work OK.

Bob
Pietro7 27 May, 2014
Hi,

Thank you very much for your message. I was succesful with the saving of the form. But the re-starting is a bit difficult for me. Should I insert a code into the "load" action for checking the user and Reading the DB? And can you please explain a bit more the "status" column thing?

Thank you very much

Peter
Max_admin 02 Jun, 2014
Hi Peter,

Each page should have a hidden field named "status", that field should hold the page number, your table should also has the field named "status", now whenever you submit a new page, the field will be updated, since you save after every page!

You will need a "db record loader" (or db read in v5) before the "html" action in the "on load", and you will need to configure it to read the logged in user's record, this is explained on many other topics and on the FAQs

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 02 Jun, 2014
Hi Max,

Thank you for your answer, I am trying to look everywhere, but I cannot find the hidden field "status" in my saved table. Is it saved somewhere else?

Thanks
Peter
Max_admin 03 Jun, 2014
Hi Peter,

You have to add it, either when you create the table in Chronoforms, or by editing the existing table using phpmyadmin in your hosting cPanel.

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 06 Jun, 2014
Hi,
First of all thank you for all your comments to my topic. But I still find some difficulties in this area and Im not being succesful in what I need. I created a field in the databasse named "status" but the value of it is always 0,and another problem is that after each save there is created a new record in the database, so I dont know how to load the page according to the status value.

Thank you very much for helping

Peter
Max_admin 06 Jun, 2014
Hi Peter,

First the new record problem, after the first save, you will have to add a hidden field to every page, the hidden field name should match the table's primary key name, in CFv4 this is most probably "cf_id".

You will also need to add the "status" field to all pages, but in each page it should be different, it should include the page's number!

Alternatively, you can add a field to your table and name it "event", that will include the page name as you set it up in the wizard!

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 01 Jul, 2014
Hi,
I have added hidden fields to my form on each page with the name and id "status", on first page the value is 1, on second 2 and so on. I have a DB save also on each page. But after submiting the second page or the whole form. The value is still 1 and doesnt change.
Then I tried to solve the new record problem. I added a hidden field to the form with the name and id "cf_id" which is my primary key. But nothing happend
Now the saving doesnt work at all, is there any maximum number of records ?

Please see the attached pictures of the configuration.

Thank you very much


Sorry about my simple questions but I am quite new to chronoforms.
Max_admin 02 Jul, 2014
Regarding the status, I think this may not work, since its value will be republished from the previous page, please remove it, and add a custom code action to every page, it should be BEFORE the "db save", and should have this code:

<?php
$form->data["status"] = 1; // change this for each page


Now the cf_id, just add a hidden field to every page and name it cf_id, leave the value empty, but check that it has been loaded on the first page ?

regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 03 Jul, 2014
Hi,

Thanks the status is now changing. But the thing with the hidden field named cf_id doesnt work, i still have more than one record. Please see the attachment.

Thank you

Peter
Max_admin 03 Jul, 2014
Please use a text field instead, name it "cf_id", now at the first page, does this field get published with the cf_id value ?

If not then how do you load the data into your form ?

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 04 Jul, 2014
Hi,

I tried to name a text box and also a text area "cf_id" but nothing appeard. Do I need to have a Load DB action ?

Thanks Peter
Max_admin 08 Jul, 2014
No, you don't need a "db loader", but a small field name mapping may be needed, please add a debugger action after the first "db save" action (first in sequence), and post the output here!

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 08 Jul, 2014
Hi,

I searched by I didnt find any event named mapping, I am adding the requested debugger output.

Thanks

Peter

Output

Data Array:

Array
(
    [chronoform] => save
    [event] => Page two
    [cf_sid] => 4102657b3cb58a041584216575db8834
    [cf_id] => 
    [sel1] => No
    [dalej] => dalej
    [c159edbc0816becee0beab6b1c355871] => 1
    [_FORM_FILES_] => Array
        (
        )

    [sel2] => Vyber
    [sel3] => Vyber
    [Koniec] => Koniec
    [status] => 1
    [chronoform_data] => Array
        (
            [cf_uid] => 281d0f11faad6fcdfd85ec4b4e451861
            [cf_created] => 2014-07-08 16:38:45
            [cf_created_by] => 235
            [cf_ipaddress] => 217.75.87.18
            [cf_user_id] => 235
            [chronoform] => save
            [event] => Page two
            [cf_sid] => 4102657b3cb58a041584216575db8834
            [cf_id] => 48
            [sel1] => No
            [dalej] => dalej
            [c159edbc0816becee0beab6b1c355871] => 1
            [_FORM_FILES_] => Array
                (
                )

            [sel2] => Vyber
            [sel3] => Vyber
            [Koniec] => Koniec
            [status] => 1
            [chronoform_data] => Array
                (
                    [cf_uid] => 926215f6efea87d6b2d7d98884ed3098
                    [cf_created] => 2014-07-08 16:37:35
                    [cf_created_by] => 235
                    [cf_ipaddress] => 217.75.87.18
                    [cf_user_id] => 235
                    [chronoform] => save
                    [event] => Page four
                    [cf_sid] => 2205f1f0ce6cce6912b87182c7418c61
                    [cf_id] => 47
                    [sel3] => Vyber
                    [Koniec] => Koniec
                    [c159edbc0816becee0beab6b1c355871] => 1
                    [_FORM_FILES_] => Array
                        (
                        )

                    [sel1] => No
                    [dalej] => dalej
                    [sel2] => Vyber
                    [status] => 3
                )

            [chronoform_data_cf_id] => 47
        )

    [chronoform_data_cf_id] => 48
)
Validation Errors:
Array
(
)
Max_admin 10 Jul, 2014
Ok, assuming all your pages have a field named "cf_id", just add a "custom code" action after the first "db save" action and use this code:

<?php
$form->data["cf_id"] = $form->data["chronoform_data_cf_id"];
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
Pietro7 11 Jul, 2014
Hi,

Thanks now it is working, I have only one record after submitting the whole form. But there is another problem, that I have only one record even when I change the user, which isnt good for me, because my aim is that each user will have the option to save the form and return to it afterwards.
Could you please give me some hints to this also?

Thank you

Peter
Max_admin 19 Jul, 2014
Hi Peter,

This depends on how your reload the data first, CF stores the logged in user id under "cf_user_id", so you will have to use this field when you load the data, using the "WHERE SQL" box in the "db record loader", or how do you load the data ?

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
cedric755 10 Nov, 2014
Hi,

I'm trying to get things worked as mentionned in this topic, with CFV4 on Joomla 1.5.26
I've set up a multipage form with 10 pages, each page is saved with Db Save action, after each Db Save i add the custom code
"<?php
$form->data["cf_id"] = $form->data["chronoform_data_cf_id"];"
i've exactly followed the step by step of this topic but Unfortunately, I'm stuck with the CF_id, I supposed...
If it may help You'll find enclosed a back up
[attachment=0]CFV4_FormsBackup_ON_graphi-net.fr_10_Nov_2014_11-34-21.cf4bak[/attachment]

All my pages are saving ok into MYSQL, but if i tried to modify them in the front end, it creates a new record, even when i use the back button

Any help would really beusefull

Thanks by advance
Max_admin 10 Nov, 2014
Hi Cedric,

So, all your pages are saved to the same record in mySQL, but the problem is when you try to edit the record later in your form ?

If yes then please make sure that your first page has a hidden field named "cf_id"

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
cedric755 10 Nov, 2014
Thanks for you reply,

In fact no
Each pages has his own table, so i have 9 tables

Each page has a hidden field "cf_id" in elements

And each pages has a custom code "<?php
$form->data['cf_id'] = $form->data['chronoform_data']['cf_id'];
?>" in Action
cedric755 10 Nov, 2014
Please find enclosed the saving of my all form it would be easier to understand than my explanation
cedric755 10 Nov, 2014

Hi Petro7,

Add a submit button to your form, use a DB Save action to save the results so far. I'd do this with any multi-page form.

Re-starting is a little tricker. You need to identify the user, get the saved form data with a DB Read action, then redirect to the appropriate form page.

I think I would use a 'status' column in the database record to record the last page saved; that would work OK.

Bob



Hi Greyhead,

I come to you so far after reading the good post "Save and get data in a multi page form" but unfortunately I wasn't abble to succeed.

To make myself as clear as possible you'll find enclosed a backup form on which I'm stuck.

In fact I've, as you suggest a multipage with, for each page a DB save, with a custom action Cf_id Action for each and so on

Please Help me I'm about to crash down

Thanks by advance

Regards
cedric755 10 Nov, 2014
Sorry to bother you again,

I'm still investigating the problem

What I find so far is
when using the go back button it's create a new record after resubmittinig it

When I logout and just after I login it updates successfully :
For doing so
I suppress all the custom action cf_id after each Db save and just add one at the end of the process that is to say on the last page Cause I noticed that when we put it under the first DB acton it block all process

If you have any advice I would very much appreciate

Sorry If my first post were a bit rude

Regards
Max_admin 11 Nov, 2014
Hi Cedric,

Do you really want to save the data to 1 table for each page ?

If the answer is yes and you want to be able to edit the data later then you only need to have a "cf_id" field in each page, and you should remove the "Custom code" you have since this is a for a different thing!

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
cedric755 11 Nov, 2014
Thank you for answering me,

I arrived at the same conclusion as you,
Now Db are saving Ok, (I was doing it in a wrong way cause i first copy the same Table DB for each page instead of using a required a specific one for each page)
I can Update without creating a new record after logout/login
I can use the go back button to also update the previous form

Nevertheless, I'm trying now to understand thanks to the status action, how to load the page, where the customer has stopped to fill the field.

So for doing it I put at the beginning of Actions in each page the custom code " <?php $form->data["status"] = 1;
?> " as mentionned in this topic.

For the moment it doesn't work, but I'm still searching, and I really appreciate that you are taking care of my concern, to be supported is sometimes a good thing

Thanks by advance if you have allready find the trick I'm looking for (status)

Regards
cedric755 11 Nov, 2014
I just find some others issues

For example when a person login to complete the form, everything is going right, except that when he uses the go back button, it creates a new table in the DB, I don't get it

Second when a person login to fill the form let's say till page 3, and then logout, to fill the form again by login, the data from page 1 to 3 will be saved in DB, but from page 4 to 9 they won't be, it's like it was locked, at page 3 where he logged out.

I haven't yet find the way to access thanks to the Action status, to the page where the person stop to fill the form by logging out.

Hope I don't bother to much anyway I'm still testing

Regards
GreyHead 12 Nov, 2014
Hi cedric755,

You have to have a way to identify the user and the records from their form between pages and between sessions.

When a user logs out any temporary data that ChronoForms has is deleted, it is not available when they log in again.

As they are logged in you can use their User ID to recover data that has been saved in the form table or tables. But you have to know which record to recover if there is more than one.

Is there a good reason for using separate tables for each page of your form instead of one table for all of the pages?

Bob
cedric755 12 Nov, 2014
Hi,

Thanks for the reply,

For answering to your Poste regarding :

1- "You have to have a way to identify the user and the records from their form between pages and between sessions."
I'm doing it with a DB record loader with request param user_id and a DB save for each page

2- "When a user logs out any temporary data that ChronoForms has is deleted, it is not available when they log in again."
Thanks to the Bd Record Loader the user can retrieve his data with user_id request param and DB Save

3- "As they are logged in you can use their User ID to recover data that has been saved in the form table or tables. But you have to know which record to recover if there is more than one."
Each page has his own table and this is working ok for the recovering

-4 "is there a good reason for using separate tables for each page of your form instead of one table for all of the pages?"
Yes my multipage form is made for user who want to filled it out at different time, so for example they can log out on page 3 and then they'll be abble to login to finish to filled out the rest of the form

I don't know where i did a mistake, but for example if a user login and fills the form till page 3 and then suddendly want to change the form from page 2 by using the back button, it creates a new record in the tables of page 2 (cf-id2 ) instead of updating the record in the table cf_id1

Also when a user came back after a while to fill the multipage form by login again and let say he has stopped first on page 3 and then logout, he can update the tables from page1 to 3 but he can't get table recorded for the other pages, no record seems available it's like it is locked

You'll find enclosed my multipage form it should be clearest
[attachment=0]CFV4_FormsBackup_ON_graphi-net.fr_12_Nov_2014_10-57-06.cf4bak[/attachment]

Regarding the db I give you it, here :

-- phpMyAdmin SQL Dump
-- version 3.4.11.1deb2
-- http://www.phpmyadmin.net
--
-- Client: localhost
-- Généré le: Mer 12 Novembre 2014 à 10:59
-- Version du serveur: 5.5.37
-- Version de PHP: 5.4.17-1~dotdeb.1

SET FOREIGN_KEY_CHECKS=0;
SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT=0;
START TRANSACTION;
SET time_zone = "+00:00";


/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;

--
-- Base de données: `c2collegeidf`
--

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_1`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_1`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_1` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `NomEnfant` varchar(255) NOT NULL,
  `PrenomEnfant` varchar(255) NOT NULL,
  `AdresseEnfant` varchar(255) NOT NULL,
  `DatedeNaissanceEnfant` varchar(255) NOT NULL,
  `LieudeNaissanceEnfant` varchar(255) NOT NULL,
  `ClasseEnfant` varchar(255) NOT NULL,
  `PAI` varchar(255) NOT NULL,
  `EtatCivilDesRepresentsLegaux` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_2`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_2`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_2` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `NomRepresentantLegal` varchar(255) NOT NULL,
  `PrenomRepresentantLegal` varchar(255) NOT NULL,
  `AdresseRepresentantLegal` varchar(255) NOT NULL,
  `TelephoneFixeRepresentantLegal` varchar(255) NOT NULL,
  `TelephoneBureauRepresentantLegal` varchar(255) NOT NULL,
  `CourrielRepresentantLegal` varchar(255) NOT NULL,
  `MedecinTraitant` varchar(255) NOT NULL,
  `RenseignementsAdministratifs` varchar(255) NOT NULL,
  `back` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_3`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_3`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_3` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `NumeroSSEnfant` varchar(255) NOT NULL,
  `NomNumeroMutuelle` varchar(255) NOT NULL,
  `NumeroAllocataire` varchar(255) NOT NULL,
  `CompagnieResponsabiliteCivile` varchar(255) NOT NULL,
  `AdresseResponsabiliteCivile` varchar(255) NOT NULL,
  `NumeroContratResponsabiliteCivile` varchar(255) NOT NULL,
  `ReglementInterieur` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_4`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_4`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_4` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `SoussigneNomPrenomRepresentantlegal` varchar(255) NOT NULL,
  `DelEnfantRepresentantlegal` varchar(255) NOT NULL,
  `DeclareRepresentantlegal` varchar(255) NOT NULL,
  `DechargeDeResponsabilite` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_5`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_5`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_5` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `DechargeResponsabilitéNom` varchar(255) NOT NULL,
  `DechargeResponsabiliteEnfantNom` varchar(255) NOT NULL,
  `DechargedeResponsabiliteAccompagnede` varchar(255) NOT NULL,
  `RentrerparSesPropresMoyens` varchar(255) NOT NULL,
  `ParticiperaToutesActivites` varchar(255) NOT NULL,
  `SortiesAvecIntervenants` varchar(255) NOT NULL,
  `PhotographieFilme` varchar(255) NOT NULL,
  `SeRendreAvecAniamteurs` varchar(255) NOT NULL,
  `Maquille` varchar(255) NOT NULL,
  `SoussigneDechargeResponsabilite` varchar(255) NOT NULL,
  `FicheSanitaire` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_6`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_6`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_6` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `Diphterie` varchar(255) NOT NULL,
  `Tetanos` varchar(255) NOT NULL,
  `Poliomyelite` varchar(255) NOT NULL,
  `DTPolio` varchar(255) NOT NULL,
  `Tetracoq` varchar(255) NOT NULL,
  `HepatiteB` varchar(255) NOT NULL,
  `RubeoleOreillonRougeole` varchar(255) NOT NULL,
  `Coqueluche` varchar(255) NOT NULL,
  `Autres` varchar(255) NOT NULL,
  `RenseignementMedicaux` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_7`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_7`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_7` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `TraitementMedicalSejour` varchar(255) NOT NULL,
  `Rubeole` varchar(255) NOT NULL,
  `Varicelle` varchar(255) NOT NULL,
  `Angine` varchar(255) NOT NULL,
  `Scarlatine` varchar(255) NOT NULL,
  `Rhumatisme` varchar(255) NOT NULL,
  `Otite` varchar(255) NOT NULL,
  `Rougeole` varchar(255) NOT NULL,
  `Asthme` varchar(255) NOT NULL,
  `Medicamenteuses` varchar(255) NOT NULL,
  `Alimentaires` varchar(255) NOT NULL,
  `AutresAllergies` varchar(255) NOT NULL,
  `CauseAllergie` varchar(255) NOT NULL,
  `DifficultesSante` varchar(255) NOT NULL,
  `RecommandationsUtilesParents` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_8`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_8`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_8` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `RecommandationsUtiles` varchar(255) NOT NULL,
  `PlanningSeptembre14` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_9`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_9`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_9` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `PlanningSeptembre14` varchar(255) NOT NULL,
  `CinqSeptembre` varchar(255) NOT NULL,
  `DouzeSeptembre` varchar(255) NOT NULL,
  `DixNeufSeptembre` varchar(255) NOT NULL,
  `VingtSixSeptembre` varchar(255) NOT NULL,
  `TroisOctobre` varchar(255) NOT NULL,
  `DixOctobre` varchar(255) NOT NULL,
  `DixSeptOctobre` varchar(255) NOT NULL,
  `SeptNovembre` varchar(255) NOT NULL,
  `QuatorzeNovembre` varchar(255) NOT NULL,
  `VingtUnNovembre` varchar(255) NOT NULL,
  `VingtHuitNovembre` varchar(255) NOT NULL,
  `CinqDecembre` varchar(255) NOT NULL,
  `DouzeDecembre` varchar(255) NOT NULL,
  `DixNeufDecembre` varchar(255) NOT NULL,
  `PhotoEnfant` varchar(255) NOT NULL,
  `Envoyez` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_10`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_10`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_10` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `NomEnfant` varchar(255) NOT NULL,
  `PrenomEnfant` varchar(255) NOT NULL,
  `AdresseEnfant` varchar(255) NOT NULL,
  `DatedeNaissanceEnfant` varchar(255) NOT NULL,
  `LieudeNaissanceEnfant` varchar(255) NOT NULL,
  `ClasseEnfant` varchar(255) NOT NULL,
  `PAI` varchar(255) NOT NULL,
  `EtatCivilDesRepresentsLegaux` varchar(255) NOT NULL,
  `NomRepresentantLegal` varchar(255) NOT NULL,
  `PrenomRepresentantLegal` varchar(255) NOT NULL,
  `AdresseRepresentantLegal` varchar(255) NOT NULL,
  `TelephoneFixeRepresentantLegal` varchar(255) NOT NULL,
  `TelephoneBureauRepresentantLegal` varchar(255) NOT NULL,
  `CourrielRepresentantLegal` varchar(255) NOT NULL,
  `MedecinTraitant` varchar(255) NOT NULL,
  `RenseignementsAdministratifs` varchar(255) NOT NULL,
  `back` varchar(255) NOT NULL,
  `NumeroSSEnfant` varchar(255) NOT NULL,
  `NomNumeroMutuelle` varchar(255) NOT NULL,
  `NumeroAllocataire` varchar(255) NOT NULL,
  `CompagnieResponsabiliteCivile` varchar(255) NOT NULL,
  `AdresseResponsabiliteCivile` varchar(255) NOT NULL,
  `NumeroContratResponsabiliteCivile` varchar(255) NOT NULL,
  `ReglementInterieur` varchar(255) NOT NULL,
  `SoussigneNomPrenomRepresentantlegal` varchar(255) NOT NULL,
  `DelEnfantRepresentantlegal` varchar(255) NOT NULL,
  `DeclareRepresentantlegal` varchar(255) NOT NULL,
  `DechargeDeResponsabilite` varchar(255) NOT NULL,
  `DechargeResponsabilitéNom` varchar(255) NOT NULL,
  `DechargeResponsabiliteEnfantNom` varchar(255) NOT NULL,
  `DechargedeResponsabiliteAccompagnede` varchar(255) NOT NULL,
  `RentrerparSesPropresMoyens` varchar(255) NOT NULL,
  `ParticiperaToutesActivites` varchar(255) NOT NULL,
  `SortiesAvecIntervenants` varchar(255) NOT NULL,
  `PhotographieFilme` varchar(255) NOT NULL,
  `SeRendreAvecAniamteurs` varchar(255) NOT NULL,
  `Maquille` varchar(255) NOT NULL,
  `SoussigneDechargeResponsabilite` varchar(255) NOT NULL,
  `FicheSanitaire` varchar(255) NOT NULL,
  `Diphterie` varchar(255) NOT NULL,
  `Tetanos` varchar(255) NOT NULL,
  `Poliomyelite` varchar(255) NOT NULL,
  `DTPolio` varchar(255) NOT NULL,
  `Tetracoq` varchar(255) NOT NULL,
  `HepatiteB` varchar(255) NOT NULL,
  `RubeoleOreillonRougeole` varchar(255) NOT NULL,
  `Coqueluche` varchar(255) NOT NULL,
  `Autres` varchar(255) NOT NULL,
  `RenseignementMedicaux` varchar(255) NOT NULL,
  `TraitementMedicalSejour` varchar(255) NOT NULL,
  `Rubeole` varchar(255) NOT NULL,
  `Varicelle` varchar(255) NOT NULL,
  `Angine` varchar(255) NOT NULL,
  `Scarlatine` varchar(255) NOT NULL,
  `Rhumatisme` varchar(255) NOT NULL,
  `Otite` varchar(255) NOT NULL,
  `Rougeole` varchar(255) NOT NULL,
  `Asthme` varchar(255) NOT NULL,
  `Medicamenteuses` varchar(255) NOT NULL,
  `Alimentaires` varchar(255) NOT NULL,
  `AutresAllergies` varchar(255) NOT NULL,
  `CauseAllergie` varchar(255) NOT NULL,
  `DifficultesSante` varchar(255) NOT NULL,
  `RecommandationsUtilesParents` varchar(255) NOT NULL,
  `RecommandationsUtiles` varchar(255) NOT NULL,
  `PlanningSeptembre14` varchar(255) NOT NULL,
  `CinqSeptembre` varchar(255) NOT NULL,
  `DouzeSeptembre` varchar(255) NOT NULL,
  `DixNeufSeptembre` varchar(255) NOT NULL,
  `VingtSixSeptembre` varchar(255) NOT NULL,
  `TroisOctobre` varchar(255) NOT NULL,
  `DixOctobre` varchar(255) NOT NULL,
  `DixSeptOctobre` varchar(255) NOT NULL,
  `SeptNovembre` varchar(255) NOT NULL,
  `QuatorzeNovembre` varchar(255) NOT NULL,
  `VingtUnNovembre` varchar(255) NOT NULL,
  `VingtHuitNovembre` varchar(255) NOT NULL,
  `CinqDecembre` varchar(255) NOT NULL,
  `DouzeDecembre` varchar(255) NOT NULL,
  `DixNeufDecembre` varchar(255) NOT NULL,
  `PhotoEnfant` varchar(255) NOT NULL,
  `Envoyez` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Structure de la table `stlaurent_chronoforms_data_11`
--

DROP TABLE IF EXISTS `stlaurent_chronoforms_data_11`;
CREATE TABLE IF NOT EXISTS `stlaurent_chronoforms_data_11` (
  `cf_id` int(11) NOT NULL AUTO_INCREMENT,
  `cf_uid` varchar(255) NOT NULL,
  `cf_created` datetime NOT NULL,
  `cf_modified` datetime NOT NULL,
  `cf_created_by` int(11) NOT NULL,
  `cf_modified_by` int(11) NOT NULL,
  `cf_ipaddress` varchar(255) NOT NULL,
  `cf_user_id` int(11) NOT NULL,
  `user_id` varchar(255) NOT NULL,
  `status` varchar(255) NOT NULL,
  `NomEnfant` varchar(255) NOT NULL,
  `PrenomEnfant` varchar(255) NOT NULL,
  `AdresseEnfant` varchar(255) NOT NULL,
  `DatedeNaissanceEnfant` varchar(255) NOT NULL,
  `LieudeNaissanceEnfant` varchar(255) NOT NULL,
  `ClasseEnfant` varchar(255) NOT NULL,
  `PAI` varchar(255) NOT NULL,
  `EtatCivilDesRepresentsLegaux` varchar(255) NOT NULL,
  `NomRepresentantLegal` varchar(255) NOT NULL,
  `PrenomRepresentantLegal` varchar(255) NOT NULL,
  `AdresseRepresentantLegal` varchar(255) NOT NULL,
  `TelephoneFixeRepresentantLegal` varchar(255) NOT NULL,
  `TelephoneBureauRepresentantLegal` varchar(255) NOT NULL,
  `CourrielRepresentantLegal` varchar(255) NOT NULL,
  `MedecinTraitant` varchar(255) NOT NULL,
  `RenseignementsAdministratifs` varchar(255) NOT NULL,
  `back` varchar(255) NOT NULL,
  `NumeroSSEnfant` varchar(255) NOT NULL,
  `NomNumeroMutuelle` varchar(255) NOT NULL,
  `NumeroAllocataire` varchar(255) NOT NULL,
  `CompagnieResponsabiliteCivile` varchar(255) NOT NULL,
  `AdresseResponsabiliteCivile` varchar(255) NOT NULL,
  `NumeroContratResponsabiliteCivile` varchar(255) NOT NULL,
  `ReglementInterieur` varchar(255) NOT NULL,
  `SoussigneNomPrenomRepresentantlegal` varchar(255) NOT NULL,
  `DelEnfantRepresentantlegal` varchar(255) NOT NULL,
  `DeclareRepresentantlegal` varchar(255) NOT NULL,
  `DechargeDeResponsabilite` varchar(255) NOT NULL,
  `DechargeResponsabilitéNom` varchar(255) NOT NULL,
  `DechargeResponsabiliteEnfantNom` varchar(255) NOT NULL,
  `DechargedeResponsabiliteAccompagnede` varchar(255) NOT NULL,
  `RentrerparSesPropresMoyens` varchar(255) NOT NULL,
  `ParticiperaToutesActivites` varchar(255) NOT NULL,
  `SortiesAvecIntervenants` varchar(255) NOT NULL,
  `PhotographieFilme` varchar(255) NOT NULL,
  `SeRendreAvecAniamteurs` varchar(255) NOT NULL,
  `Maquille` varchar(255) NOT NULL,
  `SoussigneDechargeResponsabilite` varchar(255) NOT NULL,
  `FicheSanitaire` varchar(255) NOT NULL,
  `Diphterie` varchar(255) NOT NULL,
  `Tetanos` varchar(255) NOT NULL,
  `Poliomyelite` varchar(255) NOT NULL,
  `DTPolio` varchar(255) NOT NULL,
  `Tetracoq` varchar(255) NOT NULL,
  `HepatiteB` varchar(255) NOT NULL,
  `RubeoleOreillonRougeole` varchar(255) NOT NULL,
  `Coqueluche` varchar(255) NOT NULL,
  `Autres` varchar(255) NOT NULL,
  `RenseignementMedicaux` varchar(255) NOT NULL,
  `TraitementMedicalSejour` varchar(255) NOT NULL,
  `Rubeole` varchar(255) NOT NULL,
  `Varicelle` varchar(255) NOT NULL,
  `Angine` varchar(255) NOT NULL,
  `Scarlatine` varchar(255) NOT NULL,
  `Rhumatisme` varchar(255) NOT NULL,
  `Otite` varchar(255) NOT NULL,
  `Rougeole` varchar(255) NOT NULL,
  `Asthme` varchar(255) NOT NULL,
  `Medicamenteuses` varchar(255) NOT NULL,
  `Alimentaires` varchar(255) NOT NULL,
  `AutresAllergies` varchar(255) NOT NULL,
  `CauseAllergie` varchar(255) NOT NULL,
  `DifficultesSante` varchar(255) NOT NULL,
  `RecommandationsUtilesParents` varchar(255) NOT NULL,
  `RecommandationsUtiles` varchar(255) NOT NULL,
  `PlanningSeptembre14` varchar(255) NOT NULL,
  `CinqSeptembre` varchar(255) NOT NULL,
  `DouzeSeptembre` varchar(255) NOT NULL,
  `DixNeufSeptembre` varchar(255) NOT NULL,
  `VingtSixSeptembre` varchar(255) NOT NULL,
  `TroisOctobre` varchar(255) NOT NULL,
  `DixOctobre` varchar(255) NOT NULL,
  `DixSeptOctobre` varchar(255) NOT NULL,
  `SeptNovembre` varchar(255) NOT NULL,
  `QuatorzeNovembre` varchar(255) NOT NULL,
  `VingtUnNovembre` varchar(255) NOT NULL,
  `VingtHuitNovembre` varchar(255) NOT NULL,
  `CinqDecembre` varchar(255) NOT NULL,
  `DouzeDecembre` varchar(255) NOT NULL,
  `DixNeufDecembre` varchar(255) NOT NULL,
  `PhotoEnfant` varchar(255) NOT NULL,
  `Envoyez` varchar(255) NOT NULL,
  PRIMARY KEY (`cf_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
SET FOREIGN_KEY_CHECKS=1;
COMMIT;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
Max_admin 12 Nov, 2014
Hi Cedric,

Saving the form at each page needs careful setup, specially if you are saving it to multiple tables, you may need to check the page from which the user is coming before saving, which means some PHP code dependent on the buttons names.

Could you try to create 1 table for all pages and use that ?

regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
cedric755 13 Nov, 2014
Hi Max,
thanks for answering me,

The aim of my form is that people can stop whenever they want to fill it in, so unfortunately I don't think it woul be possible to try with 1 table for all pages,
Nevertheless if you confirm me that it's possible to let the user come back to the form where he has stopped to fill in, I'll try to create 1 table for all pages

If you can't help me on this, please tell me so,
andin that case I would vrey much appreciate that you advise me someone that can handle it, even if it's a paid solution.

By advance thank you Max

Is Bob think the same as you, cause he seems to be the one who canhandle it???

Regards

Cedric
cedric755 13 Nov, 2014
Hi,

I almost resolved all my issues so far

The only thing i'm looking for Now, it is an explanation regarding 'status'

I don't get it

How the user can go back after logout/login, to the page of the form he has stop to fill ed in.

An explanation would be very much appreciated

Thanks
Max_admin 25 Nov, 2014
Hi Cedric,

Apologizes for not replying sooner!

Just add 1 more field to your table and name it "event", and that will save the last step the user accessed!

But in order to send the user to this page later, you will need some trick using a different form!

Regards,
Max
Max, ChronoForms developer
ChronoMyAdmin: Database administration within Joomla, no phpMyAdmin needed.
ChronoMails simplifies Joomla email: newsletters, logging, and custom templates.
This topic is locked and no more replies can be posted.