S
SonOfXavier
Hello All,
I have been developing a few of applications with the OWC Pivot tables, but
I have just started to encounter a problem that I am not sure how to deal
with and was hoping you might have a clue on how to solve it.
In the last three month or so, clients/users/developers have been
encountering a problem with the OWC Pivot where, when they select either the
AutoCalc button or the Commands and Options button from the Toolbar or the
right-click menu, the Internet explorer or the application closes on them.
This is not a consistent problem. Sometimes they can press the button and
nothing happens and sometimes it blows up.
Has anyone else encountered this problem? Does anyone have a solution?
By the way, I have been writing applications using OWC in VB6 for a couple
of year now and I have never seen this problem. The clients/users (approx. 70
users) are still using the VB6 version application and have never seen this
problem. The problem is occurring with applications and web sites that have
been developed using .Net on some workstations. We are using OWC10, because
we haven’t upgraded yet.
Thanks,
Gordon
Statistics Canada
PS Congratulations on your book Alvin
I have been developing a few of applications with the OWC Pivot tables, but
I have just started to encounter a problem that I am not sure how to deal
with and was hoping you might have a clue on how to solve it.
In the last three month or so, clients/users/developers have been
encountering a problem with the OWC Pivot where, when they select either the
AutoCalc button or the Commands and Options button from the Toolbar or the
right-click menu, the Internet explorer or the application closes on them.
This is not a consistent problem. Sometimes they can press the button and
nothing happens and sometimes it blows up.
Has anyone else encountered this problem? Does anyone have a solution?
By the way, I have been writing applications using OWC in VB6 for a couple
of year now and I have never seen this problem. The clients/users (approx. 70
users) are still using the VB6 version application and have never seen this
problem. The problem is occurring with applications and web sites that have
been developed using .Net on some workstations. We are using OWC10, because
we haven’t upgraded yet.
Thanks,
Gordon
Statistics Canada
PS Congratulations on your book Alvin