Charlotte Foust
charlotte.foust at gmail.com
Mon Dec 15 12:43:38 CST 2014
I've seen the error in reportview before. It seems that ReportView is sort of a hybrid between forms and reports. I stopped using the double click and put a button on to trigger the action I wanted. I didn't have time to research it and find a solution, so I worked around it. Charlotte On Sun, Dec 14, 2014 at 2:23 PM, Susan Harkins <ssharkins at gmail.com> wrote: > > Scratch all that. > > It was working beautiful and all the sudden... it's back. :( The report is > definitely in Report View. <sigh> > > Susan H. > > On Sun, Dec 14, 2014 at 2:21 PM, Susan Harkins <ssharkins at gmail.com> > wrote: > > > > Nevermind... I often miss the forest for the trees. > > > > The clue was right there -- can't execute code in design mode. I wasn't > in > > design mode, I was in Report View so the error message seemed confused. > > > > I was confused. I was in Layout View. > > > > Criminy... > > > > Susan H. > > > > On Sun, Dec 14, 2014 at 1:58 PM, Susan Harkins <ssharkins at gmail.com> > > wrote: > >> > >> A double-click event procedure returns the error that I can't execute > >> code in Design view. So... if there's a double-click event in the > module, > >> but I can't execute, what's next? > >> > >> I think I remember something about putting the report in Design view to > >> make the change, but there's no code, I just dropped the event in -- > >> nothing's running. Triggering the event alone is producing the error. > >> > >> A bit of research later -- I'm not closer to figuring it out. > >> > >> Thanks for any help. > >> > >> Susan H. > >> > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >