Hi
i had a few more or less complicated Questions:
Autocomplete
did i need for every Autocomplete Processor an own Event or can i use the same Event for all Autocomplete Processor?
Why both (Processor and Loader) had Field Name, Min-length and max-choice inside and not only one of this?
i had several Input-Fields at the same page, 3 of it should use a Autocomplete Loader.
they load 3 different columns of the same db-table.
Generally to do that i need :
3 Autocomplete Loader before the show html Action. 3 different Events, each with a single Autocomplete Processor in it?
is that Correct? or is there a more simple way to do that?
DB-Save
I had a form with 2 DB-Save actions, one save to a table created by chronoforms, one should save to a separate table of the same DB.
somehow the save-action for the separate table only works when a record exist that had the same primary-key like the one that i would save. the primary-key of the separate table is a int(11), and the value came from a hidden field inside the form.
of course the record for the chronoforms table are always created, no matter if the other db-save work or not. save order doesnt matter.
the debugger shows no error.
that means i could update existing records at the second table, but i cant create new records.
Someone had a clue what i did wrong? or why the second table is able to update existing records, but cant create new record in it.
Best Regards and thanks for every help
grafik
i had a few more or less complicated Questions:
Autocomplete
did i need for every Autocomplete Processor an own Event or can i use the same Event for all Autocomplete Processor?
Why both (Processor and Loader) had Field Name, Min-length and max-choice inside and not only one of this?
i had several Input-Fields at the same page, 3 of it should use a Autocomplete Loader.
they load 3 different columns of the same db-table.
Generally to do that i need :
3 Autocomplete Loader before the show html Action. 3 different Events, each with a single Autocomplete Processor in it?
is that Correct? or is there a more simple way to do that?
DB-Save
I had a form with 2 DB-Save actions, one save to a table created by chronoforms, one should save to a separate table of the same DB.
somehow the save-action for the separate table only works when a record exist that had the same primary-key like the one that i would save. the primary-key of the separate table is a int(11), and the value came from a hidden field inside the form.
of course the record for the chronoforms table are always created, no matter if the other db-save work or not. save order doesnt matter.
the debugger shows no error.
that means i could update existing records at the second table, but i cant create new records.
Someone had a clue what i did wrong? or why the second table is able to update existing records, but cant create new record in it.
Best Regards and thanks for every help
grafik