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
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Index corruption (ADS)
- ignacio
- Site Admin
- Mensajes: 9259
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
Index corruption (ADS)
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
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
Index corruption (ADS)
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
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
-
- Mensajes: 115
- Registrado: Jue Jun 01, 2006 7:21 pm
Index corruption (ADS)
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
>
>
>
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
>
>
>
-
- Mensajes: 115
- Registrado: Jue Jun 01, 2006 7:21 pm
Index corruption (ADS)
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
>
>
>
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
>
>
>