Apologies for waisting your time. The new day has opened my eyes. I had a db.db.sometable (result of a manual copy and paste) later on in the function which caused this db-problem.
There is still another problem but I will first try and out what is going on here. Thanks for your attention to help me. Johann On 8 February 2018 at 08:03, Johann Spies <johann.sp...@gmail.com> wrote: > On 7 February 2018 at 22:14, Dave S <snidely....@gmail.com> wrote: >> >> >> I thought web2py always ran the model files before calling the controller >> function, >> part of the overhead of each call (and the reason for lazy tables and tables >> defined in modules). >> >> Johann, is this function in the file named in the traceback, >> controllers/indicators.py? > > Yes. It is early morning now. I will experiment further and try and > find what is going on. > > Regards. > Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
