From what I have read, the Migration Wizard from VB6 to .Net is somewhat
limited in ability.
- Do not expect it to convert everything.
- Do expect to have to check every line of code and correct/re-write.

NickHK

"Nay" wrote in message
...
Hi
I have used the VS2005 imigration wizard to imigrate a VB6.0 project that:
- Build dynamic workbook by the xml, and save it as "myExcel.xls"
- Manipulate it via automation

It all used to work fine in vb6.0

1)The VB6.0 classes have used msxml dom objects and were converted to
interop
But Now the xml lines are to long(before they were broked down)the
2) After the file is created I ask for some values, If the cell value is
extracted from an escel function it will give an error value(#NA). Of
course
the automation classes were converted to interop as well

Any idea?