C
Clodoaldo
Hi,
I´ve built an application in vb.net that exports some values to an Excel
pivot table using office pia´s, and when I try to set the
PivotField.Orientation property a value like
Excel.XlPivotFieldOrientation.xlColumnField, I get the following error:
Unhandled Exception: System.Runtime.InteropServices.COMException
(0x800A03EC): It´s not possible to set the Orientation property in the
PivotField class.
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object
o, Type& objType, String name, Object[] args, String[] paramnames, Boolean
OptimisticSet, CallType UseCallType)
at Microsoft.VisualBasic.CompilerServices.LateBinding.LateSetComplex(Object
o, Type objType, String name, Object[] args, String[] paramnames, Boolean
OptimisticSet, Boolean RValueBase)
It seems to be a version problem between my PIA´s and the installed version
of ms office, but I´m not quite sure about that. For now, I´ve made some
tests with office 2000 and 2003. For both of them, I´ve got the same
exception.
Another strange issue is that, if I run the same code in VBA, it works fine.
Does anybody have a clue?
I´ve built an application in vb.net that exports some values to an Excel
pivot table using office pia´s, and when I try to set the
PivotField.Orientation property a value like
Excel.XlPivotFieldOrientation.xlColumnField, I get the following error:
Unhandled Exception: System.Runtime.InteropServices.COMException
(0x800A03EC): It´s not possible to set the Orientation property in the
PivotField class.
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object
o, Type& objType, String name, Object[] args, String[] paramnames, Boolean
OptimisticSet, CallType UseCallType)
at Microsoft.VisualBasic.CompilerServices.LateBinding.LateSetComplex(Object
o, Type objType, String name, Object[] args, String[] paramnames, Boolean
OptimisticSet, Boolean RValueBase)
It seems to be a version problem between my PIA´s and the installed version
of ms office, but I´m not quite sure about that. For now, I´ve made some
tests with office 2000 and 2003. For both of them, I´ve got the same
exception.
Another strange issue is that, if I run the same code in VBA, it works fine.
Does anybody have a clue?