Hi, migrating power builder application from PB 11.5 to PB 17 (2017) getting error accessing object windows 10. need urgent help on this why this error comes is this related to any registry or OLE registry missing. Quick help on this is really appreciated.
-
amit kurhe
- PowerBuilder
- Friday, 13 September 2019 00:57 AM UTC
Comment
- Michael Kramer
- Friday, 13 September 2019 16:59 PM UTC
Connectivity can be hard!
Sorry, but my instinct tells me O365 as installed on that machine behaves different than your PB app expects.
Names like OLE_Progress and OLE_1 leave very little hint at where to look since OLEObject can connect to "anything".
First place to look: ConnectToNewObject / ConnectToObject >> Is the "classname" valid on that machine? O365 may expose different classnames that your app requests.
Next place(s) to look is where your app calls that OLEObject. You will need to check that the calls are actually valid for O365. Microsoft publishes lots of docs online. You will need to verify that the function calls and property settings your PB code accesses are valid in O365.
I know, tedious work but you need to figure out when things go wrong. Your app may crash to do something gone many code lines prior to the crash.
HTH /Michael
Sorry, but my instinct tells me O365 as installed on that machine behaves different than your PB app expects.
Names like OLE_Progress and OLE_1 leave very little hint at where to look since OLEObject can connect to "anything".
First place to look: ConnectToNewObject / ConnectToObject >> Is the "classname" valid on that machine? O365 may expose different classnames that your app requests.
Next place(s) to look is where your app calls that OLEObject. You will need to check that the calls are actually valid for O365. Microsoft publishes lots of docs online. You will need to verify that the function calls and property settings your PB code accesses are valid in O365.
I know, tedious work but you need to figure out when things go wrong. Your app may crash to do something gone many code lines prior to the crash.
HTH /Michael
There are no comments made yet.
Comment
- amit kurhe
- Friday, 13 September 2019 15:13 PM UTC
Hi Mike, Thanks for the reply. I am new to power builder. you may be right the issue starts when a new version of ms office (office 365) installed on the PC. the application was working fine on the windows 10 but after ms office upgrade it giving this error. any idea how to resolve this issue without upgrading the code? below line of code is causing the issue
Powerbuilder Application execution error (R0039)
error accessing external object property value at line xx
function wf_set_progress of object w_wait_prompt
code at line xx
ole_progress.object.value
other case
ole_1.object.SyncFileName
returns null (SyncFileName)
Thanks for your help in advance.
Powerbuilder Application execution error (R0039)
error accessing external object property value at line xx
function wf_set_progress of object w_wait_prompt
code at line xx
ole_progress.object.value
other case
ole_1.object.SyncFileName
returns null (SyncFileName)
Thanks for your help in advance.
There are no comments made yet.
Comment
- amit kurhe
- Monday, 16 September 2019 16:28 PM UTC
Thanks for the reply Chris, will check on those aspects. If this is the cause can we rectify without changing the PB code? by means of registry changes etc. thanks.
- David Peace (Powersoft)
- Wednesday, 18 September 2019 16:28 PM UTC
David Peace (Powersoft "The PowerBuilder & C# Experts")
If this is a basic 32-bit 64-bit issue, I guess it is, it really begs the question who is managing their IT strategy as they clearly do not understand the implications of these fundamentals. I sometimes wonder why we bother really.
Basic debugging questions:
1. What has changed? - We got that office 365
2. What's different between the old version on the new version that could be affecting my OLE integration? - Find the answer to that and you have your problem defined.
Does nobody test anything before they roll it out these days?
Sorry rant over, I'm a grumpy old git ;-)
If this is a basic 32-bit 64-bit issue, I guess it is, it really begs the question who is managing their IT strategy as they clearly do not understand the implications of these fundamentals. I sometimes wonder why we bother really.
Basic debugging questions:
1. What has changed? - We got that office 365
2. What's different between the old version on the new version that could be affecting my OLE integration? - Find the answer to that and you have your problem defined.
Does nobody test anything before they roll it out these days?
Sorry rant over, I'm a grumpy old git ;-)
- Chris Pollach @Appeon
- Thursday, 19 September 2019 14:16 PM UTC
Hi Grumpy ... your not yourself when your hungry. Try a Snickers ... https://www.youtube.com/watch?v=kZZL3ZUTrQQ
;-)
;-)
There are no comments made yet.
- Page :
- 1
There are no replies made for this question yet.
However, you are not allowed to reply to this question.
However, you are not allowed to reply to this question.