Oh, of course, changing it to m_task_cost(i, IterationCount) solved the problem. I thought I was probably missing something that should have been obvious... thanks for your help.
On Mar 16, 5:54 am, Paul Schreiner <schreiner_p...@att.net> wrote: > Oooh... that's very "old school" array callouts!!! > > If I REMEMBER correctly (18-22 years ago) > either Fortran or C+ used arrays like: > m_task_cost(i)(IterationCount) > > but VBA uses: > m_task_cost(i, IterationCount) > > thanks for the memories... (or nightmares!) > > Paul > -- ---------------------------------------------------------------------------------- Some important links for excel users: 1. Follow us on TWITTER for tips tricks and links : http://twitter.com/exceldailytip 2. Join our Facebook Group @ http://www.facebook.com/group.php?gid=287779555678 3. Excel tutorials at http://www.excel-macros.blogspot.com 4. Learn VBA Macros at http://www.quickvba.blogspot.com 5. Excel Tips and Tricks at http://exceldailytip.blogspot.com To post to this group, send email to excel-macros@googlegroups.com <><><><><><><><><><><><><><><><><><><><><><> HELP US GROW !! We reach over 6,800 subscribers worldwide and receive many nice notes about the learning and support from the group.Let friends and co-workers know they can subscribe to group at http://groups.google.com/group/excel-macros/subscribe
