I've just come across a problem entering text over 300 characters using any textbox control on a registration form. They were being truncated, but emails sent out by the form showed the text fully. When editing I could enter far larger chunks of text and the updated text worked properly.
Upon investigation I discovered the stored procedure that enters the initial response on creation, DynamicRegistration_AddDynamicResponse, had this declaration at the top
@Response as varchar(300),
Which is clearly too short to accomodate moderate descriptive text. I added a zero to this and it's stopped truncating input text, and as far as I'm aware is still shorter than the database field it stores the value in.
Is there any danger inherent in extending the length of this variable, or have I missed a setting that deal with this? If not, may I suggest that this is lengthened considerably by default in future versions of Dynamic Registration.