Xailer & OZ Software

Hello
When ever we use xHarbour (with ADS) we have this function ( AdsSetCharType(2)
) to make caracters compatible with clipper because without it there is index
corrupion if we use the same table with clipper...Now we have 2 applications
using xharbour, one with xailer and other with fivewinH...The one with FH
has a call to that function and xailer's app does not use it...bouth share
1 table...Is it possible to have index corruption in this situation? we use
NTX files.
If yes, is it possible to solve this by opening just this table in xailer
app using adsDatasource and its property nChartype set to acOEM ?
Thanks
Aguiar

Aguiar,
Xailer uses internally that function with the property nCharType, so I guess
you should just put the same value on both applications, that's all.
BTW I am not really o guru on ADS, you may ask in the xHarbour forum.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Aguiar" <[email=XPRO-00432E74-01@10.0.0.11]XPRO-00432E74-01@10.0.0.11[/email]> escribió en el mensaje
news:45619ba8$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>
> Hello
> When ever we use xHarbour (with ADS) we have this function (
> AdsSetCharType(2)
> ) to make caracters compatible with clipper because without it there is
> index
> corrupion if we use the same table with clipper...Now we have 2
> applications
> using xharbour, one with xailer and other with fivewinH...The one with FH
> has a call to that function and xailer's app does not use it...bouth share
> 1 table...Is it possible to have index corruption in this situation? we
> use
> NTX files.
> If yes, is it possible to solve this by opening just this table in xailer
> app using adsDatasource and its property nChartype set to acOEM ?
> Thanks
> Aguiar

Aguiar,
Xailer uses internally that function with the property nCharType, so I guess
you should just put the same value on both applications, that's all.
BTW I am not really o guru on ADS, you may ask in the xHarbour forum.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Aguiar" <[email=XPRO-00432E74-01@10.0.0.11]XPRO-00432E74-01@10.0.0.11[/email]> escribió en el mensaje
news:45619ba8$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>
> Hello
> When ever we use xHarbour (with ADS) we have this function (
> AdsSetCharType(2)
> ) to make caracters compatible with clipper because without it there is
> index
> corrupion if we use the same table with clipper...Now we have 2
> applications
> using xharbour, one with xailer and other with fivewinH...The one with FH
> has a call to that function and xailer's app does not use it...bouth share
> 1 table...Is it possible to have index corruption in this situation? we
> use
> NTX files.
> If yes, is it possible to solve this by opening just this table in xailer
> app using adsDatasource and its property nChartype set to acOEM ?
> Thanks
> Aguiar

Thanks Igancio. I think seting nCharType to acOEM can solve the problem.
Regards
Aguiar
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> escreveu na mensagem
news:45619fa2$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Aguiar,
>
> Xailer uses internally that function with the property nCharType, so I
> guess you should just put the same value on both applications, that's all.
>
> BTW I am not really o guru on ADS, you may ask in the xHarbour forum.
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> http://www.xailer.com
> "Aguiar" <[email=XPRO-00432E74-01@10.0.0.11]XPRO-00432E74-01@10.0.0.11[/email]> escribió en el mensaje
> news:45619ba8$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>
>> Hello
>> When ever we use xHarbour (with ADS) we have this function (
>> AdsSetCharType(2)
>> ) to make caracters compatible with clipper because without it there is
>> index
>> corrupion if we use the same table with clipper...Now we have 2
>> applications
>> using xharbour, one with xailer and other with fivewinH...The one with FH
>> has a call to that function and xailer's app does not use it...bouth
>> share
>> 1 table...Is it possible to have index corruption in this situation? we
>> use
>> NTX files.
>> If yes, is it possible to solve this by opening just this table in xailer
>> app using adsDatasource and its property nChartype set to acOEM ?
>> Thanks
>> Aguiar
>
>
>

Thanks Igancio. I think seting nCharType to acOEM can solve the problem.
Regards
Aguiar
"Ignacio Ortiz de Zúñiga" <NoName@xailer.com> escreveu na mensagem
news:45619fa2$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Aguiar,
>
> Xailer uses internally that function with the property nCharType, so I
> guess you should just put the same value on both applications, that's all.
>
> BTW I am not really o guru on ADS, you may ask in the xHarbour forum.
>
> Regards,
>
> --
> Ignacio Ortiz de Zúñiga
> http://www.xailer.com
> "Aguiar" <[email=XPRO-00432E74-01@10.0.0.11]XPRO-00432E74-01@10.0.0.11[/email]> escribió en el mensaje
> news:45619ba8$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>
>> Hello
>> When ever we use xHarbour (with ADS) we have this function (
>> AdsSetCharType(2)
>> ) to make caracters compatible with clipper because without it there is
>> index
>> corrupion if we use the same table with clipper...Now we have 2
>> applications
>> using xharbour, one with xailer and other with fivewinH...The one with FH
>> has a call to that function and xailer's app does not use it...bouth
>> share
>> 1 table...Is it possible to have index corruption in this situation? we
>> use
>> NTX files.
>> If yes, is it possible to solve this by opening just this table in xailer
>> app using adsDatasource and its property nChartype set to acOEM ?
>> Thanks
>> Aguiar
>
>
>