I knew there was a way to do that but I couldn't remember how. However, when I tried it I couldn't figure out where to put the declaration so that the report would see it. I Googled and found http://www.tek-tips.com/viewthread.cfm?qid=911454 where I chose the option of including a excluded dummy procedure in the project where the arrays are declared as public. Works great and should be easy to find if I need to do something similar again!
Thanks, Joe On Fri, Jul 3, 2015 at 12:05 PM, Ken Dibble <[email protected]> wrote: > > The only issue I have at this point is that the compiler complains each >> time because the report doesn't know that the code will create the array >> forcing me to ignore three times each time I build the project. >> > > You can stop that by issuing EXTERNAL ARRAY aMyArray in the code where the > arrays are constructed. However, it's a completely harmless compiler > warning; it has no effect on the performance of the code. I don't bother > declaring the arrays that the compiler flags. > > Ken Dibble > www.stic-cil.org > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cabqednx+_z9eqiuwt6+dzbzfhyystb3ypwyarjhgrgagfym...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
