I have a form that initially populates users first name, last name, street, city, state (read only fields) from their DNN profile.  Then, I have 12 server name submission fields and one add new 'area' question event.

If I DON'T trigger the new question event, the SQL query on from submission adds a new blank record. If I DO trigger the event and add a new 'area' name, it does NOT add any records.

Each of the 12 server name fields has a 'role' type select list next to it (pulled from a roles table).  Only the FIRST servername's selected ROLE is added to the table, all the other selections are left blank. (Each has a unique name).

After submit, the form returns with all data still shown in the fields but after submit #1, the 'City Name' now also shows up in the email address field. On submit #2, the 'City Name' now shows up in City, email address AND in the user's Last Name field. (And subsequently, the records being added have all the wrong info for email and last name now.)

Is this a bug???

 

 

This sounds like maybe the SQL Event is stopping the form from processing? Some of the last part of this post confuses me though (I read it a few times and now need some tylenol ). Could you maybe set this up on www.betasprings.com (login as host/dnnhost) or upload a picture(s) demonstrating what happening?

Well... I guess I must have taken something other than Tylenol when I was building this initial form. Very odd what was happening tho. Field1=A, Field2=B and Field3=C (all set to readonly as they firstname, lastname, street. populated from the users table) on submit would add blanks to the custom table. When the form refreshed, Field1=A, Field2=C and Field3=C, on the next refresh all Fields=C.
I threw in the towel, deleted the form and started over deciding that I didn't need to insert data I already had elsewhere, just displayed the DNN profile stuff and only insert the UserID for the new table and adding Fields D, E and F. That worked fine. Sorry for the confusing post, I couldn't understand why the fields were getting populated with the wrong data but a good nights sleep and a do-over seemed to fix it... once again.

I am not sure if this relates but if you make a field read only, the values don't seem to be available for an SQL event.
For this reason, I have mirrored read only fields with some hidden ones to allow me to save that information.