As you suggested - with little success.
If I am not mistaken you said that I could create the view as normal without using the integrator. I took that to mean that I could create a database table, then a breezing form and then a view of type breezing form which I could use in content builder. I did this and the result was a form that would not write to the content builder data storage. When I tried it the database table I created is not used, conent builder's data storage setup is not used to submit a form nor to edit a form through content builder's editable template.
This happen wether I used a content builder menu item or a breezing form's menu item.
On my own.
I had tried using the breezing form and integrator prior to this but the result was a form that would write to both data storages (breezing forms subrecords and content builder's data storage) after having setup the integrator for insert into the content builder data storage.
I had also setup the integrator to update to the content builder's data storage. When I tried to use content builder's editable template on the submitted forms, they were edited but the only storage that would get updated was the breezing forms data storage. Also when I had selected that the breezing forms would be editable by the user the same thing happened (only breezing form data storage was updated). In both cases, I was left with two data storages (content builder's and breezing forms') with inconsistant records and only the breezing forms data storage having been updated upon editing of a submitted form.
Content builder did a great job of listing and pulling up submitted forms for editing. It does appear though that those forms are pulled up from the breezing form data storage.
In summary.
In just a few form entries using breezing forms, with forms that have few elements, I have already racked up over 100 records in the subrecords data table.
I am hoping to have a website that is very form intensive and to have high volumn use of the form records. If I have many forms with many elements and many submitions this data table (subrecords) seems like it could cause problems in maintaining a swift website. This is why having the data stored in a seperate table form each form would be beneficial to my use.
I don't see how I use breezing forms to accomplish this goal using the method you suggested. I could not use the intgrator to update content builder data records despite having selected that table as the intgrators update table source and target. I don't know what I am missing. I thought that would work. I don't care if their are records in the breezing forms (subrecords) data storage so long as they and the content builder data storage can both be updated using the integrator or some other method. I need the data storages to maintain consistent data between them, since apparently there is no getting around the breezing forms data storage method.
The question.
Do you have any suggestions on how I can use the excellent breezing forms to produce many complicated forms (many page, many element) and produce a data storage that can stand the riggers of high volumn persistent use of the data by many users. It seems if I can get the data broken into a seperate table for each form that I would have the best usability.
Thanks again for any help you can give.
Jim
UPDATE INFORMATION - ADDING INTEGRATOR to BREEZING FORMS with CONTENT BUILDER DATA STORAGE
(breezing forms data storage records all behaved as expected in all cases)
Case 1: Insert and Update Intgrators Published
New Form
creates new record
updates every record with new form submission data
Update
no records created or updated
Case 2: Only Published Insert Integrator (worked as expected)
New Form
creates new record
Case 3: Only Update Integrator Published
New Form
updates every record with new form submission data
Update
no record updated
Case 4: Using the New Button Provided in the List View from Content Builder
With Published Integrators of Insert and Update, Insert Only, and Update Only
In all cases no new Content builder data storage record created.