OWC10/11.PivotTable confusion ;-)

[Harmannus]

Hallo,

I use the below code for addressing a pivot table

'Dim pTable As OWC10.PivotTable
Dim pTable As OWC11.PivotTable
Set pTable = Me.PivotTable
pTable.BackColor = 14215660
pTable.AllowCustomOrdering = False
pTable.AllowFiltering = True
pTable.AllowGrouping = False
pTable.DisplayExpandIndicator = False

When i use "Dim pTable as OCW10.PivotTable" under Acc2002 it works fine: '
removed

When i use "Dim pTable as OCW11.PivotTable" under Acc2003 i get a error on
the line Set pTable=me.PivotTable

Anybody a clue why Acc2003 states a error?

Can i add some additional code that checks for the Access version? So
Acc2002 use line 1, Acc2003 use line 2 (and a correction of line 3 of Set
pTable=me.PivotTable)

Thanx in advance for any help.

Regards,

Harmannus

 

[Michel Walsh]

Hi,

You have to use OCW10; OCW11 was reported to have incompatibility, and
OWC10, at my best knowledge, is still recommended, for Access 2003.


Hoping it may help,
Vanderghast, Access MVP

 

[Harmannus]

Hallo,

Thanx for the reply.

Access 2003 doesn't set the link to OCW10 automatically en says missing.
When i browse for the file and add it to the list it works fine.

How can i prevent this? a end-user shouldn't be have to set a reference....

Regards,
Harmannus

 

[Michel Walsh]

Hi,

You, and your client, have to have Office 2002 or 2003 in order to be able
to use PivotTables and PivotCharts. Your application should reference OWC10,
and I "assume" that even if your client has OWC11, the COM interfaces will
fallback harmoniously for the call about OWC10 interfaces, even if using
OWC11 (I am not in position to make the test). It is the same principle that
a game based on DirectX 7 interfaces is still working fine under a DirectX 9
installation. It "should" work backward (but not necessary upward, ie, a
game requiring DX9 won't probably work if only DX7 is installed; requiring
OWC11 won't work if only OWC10 is installed).



Hoping it may help,
Vanderghast, Access MVP

 

[Harmannus]

Hallo,

Well not......

In Office2002 OWC10 is referenced! Office2003 doesn't automatically
recognizes this reference and gives a error on startup! Adding the
reference, which is not present in the reference screen of Office2003, to
OWC10.dll lets the application work fine under Office2003. So i am left with
how to force Office2003 to recognize the reference.

Any suggestions?


regards,
Harmannus

 

[Michel Walsh]

HI,


The list of references are maintained "by application", I mean, if you
have a dot-mdb file with the reference, then copying your dot-mdb file
around will keep, for that application, the LIST of references it requires.

You can also add a reference through code (like AddFromGuid or
AddFromFile).


Hoping it may help,
Vanderghast, Access MVP

 

[Harmannus]

Hallo,

Well Office 2003 doesn't what OWC10 is concerned! The reference is defined
in 2002 (XP version) but when starting it under 2003 it says missing! The
OWC reference has to be added manualy. If will have a look at AddfromGuid
commands.

Regards,
Harmannus