Xailer & OZ Software

Hi Xailers!
Any news about solving the Ole problem?
The change to Harbour causes very much errors with the OleAuto they can not
be solved by using BCC instead minGW.
i.e.
oWord := CreateObject("Word.Application")
.....
oWord:Selection:ParagraphFormat:TabHangingIndent(1)
was working very well with xHarbour and BCC
Now with Harbour I get the error:
"WIN_OLEAUTO:TABHANGINGINDENT(0)
Fehler WINOLE/1007 Argument error: TABHANGINGINDENT
Argumente: ( [ 1] = Typ: N Wert: 1)
(DOS-Fehler -2147352571)"
Ole2TxtError() shows me "DISP_E_TYPEMISMATCH"
Is there any bugfixing in sight in the near future?
Why Xailer stopped supporting xHarbour?
Regards
Ingo

Ingo JH wrote on Fri, 16 August 2013 09:48Hi Xailers!
Any news about solving the Ole problem?
The change to Harbour causes very much errors with the OleAuto they can not
be solved by using BCC instead minGW.
i.e.
oWord := CreateObject("Word.Application")
.....
oWord:Selection:ParagraphFormat:TabHangingIndent(1)
was working very well with xHarbour and BCC
Now with Harbour I get the error:
"WIN_OLEAUTO:TABHANGINGINDENT(0)
Fehler WINOLE/1007 Argument error: TABHANGINGINDENT
Argumente: ( [ 1] = Typ: N Wert: 1)
(DOS-Fehler -2147352571)"
Ole2TxtError() shows me "DISP_E_TYPEMISMATCH"
Is there any bugfixing in sight in the near future?
Why Xailer stopped supporting xHarbour?
Regards
Ingo
It's a known problem, they're working on it.

Ingo,
> Hi Xailers!
>
> Any news about solving the Ole problem?
> The change to Harbour causes very much errors with the OleAuto they
> can not be solved by using BCC instead minGW.
>
> i.e.
> oWord := CreateObject("Word.Application")
> .....
> oWord:Selection:ParagraphFormat:TabHangingIndent(1)
>
> was working very well with xHarbour and BCC
>
> Now with Harbour I get the error:
> "WIN_OLEAUTO:TABHANGINGINDENT(0)
> Fehler WINOLE/1007 Argument error: TABHANGINGINDENT
> Argumente: ( [ 1] = Typ: N Wert: 1)
> (DOS-Fehler -2147352571)"
>
> Ole2TxtError() shows me "DISP_E_TYPEMISMATCH"
I though it was fixed in the library I sent you some time ago.
> Is there any bugfixing in sight in the near future?
Yes, we're trying to write our own OLE support, since those problems are
caused by the Harbour's OLE support.
> Why Xailer stopped supporting xHarbour?
The short answer: we needed it in order to keep Xailer alive. If we stay
at xHarbour, Xailer could die slowly
The long answer requires many lines
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

Jose,
sorry, the lib you sent me was libhbwin.a for minGW. But because of the
problems with hbwin_ole and minGW I'm working now with BCC instead minGW.
Any tip how to use this lib with BCC? Is it enough to change the extension
form .a to .lib?
Ok, I have to wait for Xailer's own OLE support.
The short answer about the reason of changing from xHb to Hb will do
Regards
Ingo
"Jose F. Gimenez" <jfgimenezAM]"@wanadoo.es> schrieb im Newsbeitrag
news:5211d6de$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Ingo,
>
>> Hi Xailers!
>>
>> Any news about solving the Ole problem?
>> The change to Harbour causes very much errors with the OleAuto they can
>> not be solved by using BCC instead minGW.
>>
>> i.e.
>> oWord := CreateObject("Word.Application")
>> .....
>> oWord:Selection:ParagraphFormat:TabHangingIndent(1)
>>
>> was working very well with xHarbour and BCC
>>
>> Now with Harbour I get the error:
>> "WIN_OLEAUTO:TABHANGINGINDENT(0)
>> Fehler WINOLE/1007 Argument error: TABHANGINGINDENT
>> Argumente: ( [ 1] = Typ: N Wert: 1)
>> (DOS-Fehler -2147352571)"
>>
>> Ole2TxtError() shows me "DISP_E_TYPEMISMATCH"
>
> I though it was fixed in the library I sent you some time ago.
>
>
>> Is there any bugfixing in sight in the near future?
>
> Yes, we're trying to write our own OLE support, since those problems are
> caused by the Harbour's OLE support.
>
>
>> Why Xailer stopped supporting xHarbour?
>
> The short answer: we needed it in order to keep Xailer alive. If we stay
> at xHarbour, Xailer could die slowly
>
> The long answer requires many lines
>
>
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info

Hi Jose,
could you please send me the library that fixes the problem with Ole?
Best regards, Timm.
"Jose F. Gimenez" <jfgimenezAM]"@wanadoo.es> schrieb im Newsbeitrag
news:5211d6de$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Ingo,
>
>> Hi Xailers!
>>
>> Any news about solving the Ole problem?
>> The change to Harbour causes very much errors with the OleAuto they can
>> not be solved by using BCC instead minGW.
>>
>> i.e.
>> oWord := CreateObject("Word.Application")
>> .....
>> oWord:Selection:ParagraphFormat:TabHangingIndent(1)
>>
>> was working very well with xHarbour and BCC
>>
>> Now with Harbour I get the error:
>> "WIN_OLEAUTO:TABHANGINGINDENT(0)
>> Fehler WINOLE/1007 Argument error: TABHANGINGINDENT
>> Argumente: ( [ 1] = Typ: N Wert: 1)
>> (DOS-Fehler -2147352571)"
>>
>> Ole2TxtError() shows me "DISP_E_TYPEMISMATCH"
>
> I though it was fixed in the library I sent you some time ago.
>
>
>> Is there any bugfixing in sight in the near future?
>
> Yes, we're trying to write our own OLE support, since those problems are
> caused by the Harbour's OLE support.
>
>
>> Why Xailer stopped supporting xHarbour?
>
> The short answer: we needed it in order to keep Xailer alive. If we stay
> at xHarbour, Xailer could die slowly
>
> The long answer requires many lines
>
>
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info

Ingo,
sorry for the delay. I've been offline for a few days.
> sorry, the lib you sent me was libhbwin.a for minGW. But because of
> the problems with hbwin_ole and minGW I'm working now with BCC instead
> minGW.
> Any tip how to use this lib with BCC? Is it enough to change the
> extension form .a to .lib?
here you are the lib for the two compilers:
http://www.xailer.com/files/hbwin.rar
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

Timm,
sorry for the delay.
> could you please send me the library that fixes the problem with Ole?
here you are: http://www.xailer.com/files/hbwin.rar
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

Jose,
many thanks.
Regards
Ingo
"Jose F. Gimenez" <jfgimenezAM]"@wanadoo.es> schrieb im Newsbeitrag
news:521b0b46$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Ingo,
>
> sorry for the delay. I've been offline for a few days.
>
>> sorry, the lib you sent me was libhbwin.a for minGW. But because of the
>> problems with hbwin_ole and minGW I'm working now with BCC instead minGW.
>> Any tip how to use this lib with BCC? Is it enough to change the
>> extension form .a to .lib?
>
> here you are the lib for the two compilers:
> http://www.xailer.com/files/hbwin.rar
>
>
> Regards,
>
> Jose F. Gimenez
> http://www.xailer.com
> http://www.xailer.info

Hi Jose,
the new library does not fix the error:
Subsystem Call: WINOLE
System Code: 1006
Default Status: .F.
Description: Argument error
Operation: _UNREAD
Arguments: [ 1] = Type: L Val: .F.
Involved File:
Dos Error Code: 1
Trace Through:
WIN_OLEAUTO:_UNREAD (0)
This error occurs when I try to set oItem:UnRead := .f. (MS Outlook message).
Best regards, Timm.

Timm,
> the new library does not fix the error:
>
> Subsystem Call: WINOLE
> System Code: 1006
> Default Status: .F.
> Description: Argument error
> Operation: _UNREAD
> Arguments: [ 1] = Type: L Val: .F.
> Involved File: Dos Error Code: 1
>
> Trace Through:
> WIN_OLEAUTO:_UNREAD (0)
>
> This error occurs when I try to set oItem:UnRead := .f. (MS
> Outlook message).
Ok, I see. It's exactly the same problem that DC reported a few weeks
ago. For some unknown reason to me, there are some properties that
cannot be assigned at all. It may happen with any OLE server, and the
error is always the same: the property is treated as read-only, so it
can't be assigned.
This problem didn't exist in xHarbour, and although both compilers (Hb
and xHb) have builtin OLE support based on my early work from a decade
ago, there are many differences in current implementations. I've been
researching on it, but sadly I couldn't find a fix. That's why I decided
to write our own OLE support for Xailer.
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

Jose,
ok, thanks for the answer!
I just switched that application to 2.7.5 and it works now.
Any idea when a new Xailer version with the new OLE support will be ready?
Best regards, Timm.

Hi Jose,
I still get this error using Xailer 3.2:
Subsystem Call: WINOLE
System Code: 1006
Default Status: .F.
Description: Argument error
Operation: _UNREAD
Arguments: [ 1] = Type: L Val: .F.
Involved File:
Dos Error Code: 1
Trace Through:
WIN_OLEAUTO:_UNREAD (0)
This error occurs when I try to set oItem:UnRead := .f. (MS Outlook message).
Did you perhaps fix it already?
Best regards, Timm.

Timm,
sorry for the delay...
> I still get this error using Xailer 3.2:
>
> Subsystem Call: WINOLE
> System Code: 1006
> Default Status: .F.
> Description: Argument error
> Operation: _UNREAD
> Arguments: [ 1] = Type: L Val: .F.
> Involved File: Dos Error Code: 1
>
> Trace Through:
> WIN_OLEAUTO:_UNREAD (0)
>
> This error occurs when I try to set oItem:UnRead := .f. (MS
> Outlook message).
>
> Did you perhaps fix it already?
Well, I don't remember it. Please, send me a small and self-contained
sample to check it.
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

Hi Jose,
here is an example that should mark all mails in a certain folder as read, but 'oItem3:UnRead := .f.' produces an error.
Function Test()
local oItem, oItem2, oItem3
local oOutLook := CreateObject( "OutLook.Application" )
local oNameSpace := oOutLook:GetNameSpace( "MAPI" )
oNameSpace:Logon()
for each oItem in oNameSpace:Folders
if "Postfach" $ oItem:FolderPath
for each oItem2 in oItem:Folders
if "Posteingang" $ oItem2:FolderPath

for each oItem3 in oItem2:Items
if oItem3:UnRead = .t.
oItem3:UnRead := .f.
endif
next

endif
next
endif
next
RETURN Nil
Best regards, Timm.