Hi Massimo it was a create form. I now understand why keepvalues=True as it makes sense for an edit form. The value is inconsistent between SQLFORM and FORM which may catch some people out but not sure how you address the issue.
many thanks for your quick reply. I was initially sceptical about Web2py (having used Rails/Django/Flask/Pyramid) but the more I use the framework the more I'm impressed with the ease of use and flexibility. I love the Bootstrap integration in 2.0! Keep up the amazing work. Kind Regards Dave On Thursday, June 14, 2012 6:24:25 PM UTC+1, Massimo Di Pierro wrote: > > This is the right question. I see from the source there was a change of > behavior between stable (keepvalue=False) and trunk (keepvalue=True). > > Do you have an edit form or an insert form. I this the issue was that the > behavior for edit forms was counterintuitive. > > massimo > > > On Thursday, 14 June 2012 12:11:05 UTC-5, David Simmons wrote: >> >> Hi Me again :-) >> >> Is this the wrong place to ask this question, if so I apologies and ask >> that somebody please point me to the right place for this kind of thing. >> >> Many thanks >> >> Dave >> >> On Thursday, June 14, 2012 8:08:10 AM UTC+1, David Simmons wrote: >>> >>> Hi >>> >>> I downloaded the latest trunk version of Web2py 2.0 from Github. I have >>> noticed that the keepvalues setting in SQLFORM defaults to True. This is >>> different from the setting in FORM and equally different from SQLFORM in >>> the 1.0 branch. Is this a deliberate change or a simple mistake? >>> >>> Many thanks >>> >>> Dave >>> >>
