Mike, I have encountered similar issues after clients "upgraded" to 2007 I now "auto-save" the file back to 2003 before working with the file
S On Wed, Feb 2, 2011 at 2:03 AM, MB Software Solutions, LLC < [email protected]> wrote: > We've got legacy code that ran without issue with Excel 2003 but now > it's throwing an error with this line: > > ox = This.oActiveWorkBook.Names(m.ExcelObjectName) > > the value of m.ExcelObjectName is ProvNum, which is a named range in the > Excel worksheet. > > Excel throws a 1426 error with the message being "Unknown COM status code." > > Anyone encounter this before and/or have any ideas for solution? > > Thanks, > --Mike > > > -- > Mike Babcock, MCP > MB Software Solutions, LLC > President, Chief Software Architect > http://mbsoftwaresolutions.com > http://fabmate.com > http://twitter.com/mbabcock16 > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
