Like myapp/default/display_manual_form() in the book, right? Two questions. I assume that I need a:
def data(): return dict(form=crud()) for each table that uses the crud controller to properly define the URL. If that's true, it's the part that I missed. Second, is it better to call the update directly like: 1) http://hostname/myapp/default/data/update/person/2 or create a controller like: 2) def update1(): redirect(URL(r=request,f='data/update/person/2')) In either case, what should the view be named? Since one might want to have a different view for read,update,delete,etc., it seems that it should be: default/data/update.html, but my testing seems to work at default/ data.html. That seems to imply that using method #2 above with a response.view() would be the better solution. Would you agree with that conclusion or is there a better way to handle this? Thank you. Gary On Apr 26, 9:22 pm, mdipierro <[email protected]> wrote: > Yes, you can make the form in html as usual for SQLFORM. > > On 26 Apr, 18:37, Gary <[email protected]> wrote: > > > Is there a simple way to replace the automatically generated SQLFORM > > in the various crud controllers with a custom SQLFORM? > > > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
