Página 1 de 1

TAdsDataSource.

Publicado: Jue Dic 07, 2006 3:27 pm
por pjmfelix
Hi, i have two oAdsDataSource defined in IDE.
One for use nCharType = acANSI, and the other for nCharType = acOEM.
The problem is that all oDbfDataSet stay with the property of the last.
I only resolve this, put after all oDbfDataSet:Open() the property
oDBFDataSet:oDataSource:nCharType := 1 or 2.
Why this property only work if defined in the code?
Regards.

TAdsDataSource.

Publicado: Jue Dic 07, 2006 4:02 pm
por _support_
Paulo,
I believe there is no solution for that problem because xHarbour
ADSSetChartype() function sets that value for the complete application. It
does not recognize multiple connections on the same app. You may post this
problem in xHarbour forum and ask if is possible that this functions accepts
a new parameter indicanting the connection handle.
Regards,
"Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Hi, i have two oAdsDataSource defined in IDE.
> One for use nCharType = acANSI, and the other for nCharType = acOEM.
> The problem is that all oDbfDataSet stay with the property of the last.
> I only resolve this, put after all oDbfDataSet:Open() the property
> oDBFDataSet:oDataSource:nCharType := 1 or 2.
> Why this property only work if defined in the code?
>
>
> Regards.
>

TAdsDataSource.

Publicado: Jue Dic 07, 2006 4:02 pm
por _support_
Paulo,
I believe there is no solution for that problem because xHarbour
ADSSetChartype() function sets that value for the complete application. It
does not recognize multiple connections on the same app. You may post this
problem in xHarbour forum and ask if is possible that this functions accepts
a new parameter indicanting the connection handle.
Regards,
"Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Hi, i have two oAdsDataSource defined in IDE.
> One for use nCharType = acANSI, and the other for nCharType = acOEM.
> The problem is that all oDbfDataSet stay with the property of the last.
> I only resolve this, put after all oDbfDataSet:Open() the property
> oDBFDataSet:oDataSource:nCharType := 1 or 2.
> Why this property only work if defined in the code?
>
>
> Regards.
>

TAdsDataSource.

Publicado: Jue Dic 07, 2006 4:35 pm
por Aguiar Costa
Ignacio,
What Paulo is saying is that we did some tests and it seems that having 2
Datasources 1 set to Ansi and other set to OEM (defined at IDE level), the
set that stays active is the one of the second Datasource...But if you do
the same at code level it works....can you confirm this ?
Thanks.
Aguiar !!!
"Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
> Paulo,
>
> I believe there is no solution for that problem because xHarbour
> ADSSetChartype() function sets that value for the complete application. It
> does not recognize multiple connections on the same app. You may post this
> problem in xHarbour forum and ask if is possible that this functions
> accepts a new parameter indicanting the connection handle.
>
> Regards,
>
> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>> Hi, i have two oAdsDataSource defined in IDE.
>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>> The problem is that all oDbfDataSet stay with the property of the last.
>> I only resolve this, put after all oDbfDataSet:Open() the property
>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>> Why this property only work if defined in the code?
>>
>>
>> Regards.
>>
>
>
>

TAdsDataSource.

Publicado: Jue Dic 07, 2006 4:35 pm
por Aguiar Costa
Ignacio,
What Paulo is saying is that we did some tests and it seems that having 2
Datasources 1 set to Ansi and other set to OEM (defined at IDE level), the
set that stays active is the one of the second Datasource...But if you do
the same at code level it works....can you confirm this ?
Thanks.
Aguiar !!!
"Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
> Paulo,
>
> I believe there is no solution for that problem because xHarbour
> ADSSetChartype() function sets that value for the complete application. It
> does not recognize multiple connections on the same app. You may post this
> problem in xHarbour forum and ask if is possible that this functions
> accepts a new parameter indicanting the connection handle.
>
> Regards,
>
> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>> Hi, i have two oAdsDataSource defined in IDE.
>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>> The problem is that all oDbfDataSet stay with the property of the last.
>> I only resolve this, put after all oDbfDataSet:Open() the property
>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>> Why this property only work if defined in the code?
>>
>>
>> Regards.
>>
>
>
>

TAdsDataSource.

Publicado: Vie Dic 08, 2006 9:43 am
por _support_
Aguiar,
I am not sure how it works the function ADSSetCharType(). If the function
sets a internal flag that ONLY is used on table openning, then that will be
great news, since the only thing you should do is make a call to that
function before openning any table. BTW, if that internal flag is used by
the the ADS system continously then there is nothing to do.
I suposse is the first case. If you could confirm it, I may be able to
modifiy the class so the function is called every time a dataset is going to
be openned.
Regards,
"Aguiar" <aguiar.costa@sisbit.pt> escribió en el mensaje
news:45783807$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Ignacio,
>
> What Paulo is saying is that we did some tests and it seems that having 2
> Datasources 1 set to Ansi and other set to OEM (defined at IDE level), the
> set that stays active is the one of the second Datasource...But if you do
> the same at code level it works....can you confirm this ?
> Thanks.
> Aguiar !!!
>
>
> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
> news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
>> Paulo,
>>
>> I believe there is no solution for that problem because xHarbour
>> ADSSetChartype() function sets that value for the complete application.
>> It does not recognize multiple connections on the same app. You may post
>> this problem in xHarbour forum and ask if is possible that this functions
>> accepts a new parameter indicanting the connection handle.
>>
>> Regards,
>>
>> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
>> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>> Hi, i have two oAdsDataSource defined in IDE.
>>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>>> The problem is that all oDbfDataSet stay with the property of the last.
>>> I only resolve this, put after all oDbfDataSet:Open() the property
>>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>>> Why this property only work if defined in the code?
>>>
>>>
>>> Regards.
>>>
>>
>>
>>
>
>
>

TAdsDataSource.

Publicado: Vie Dic 08, 2006 9:43 am
por _support_
Aguiar,
I am not sure how it works the function ADSSetCharType(). If the function
sets a internal flag that ONLY is used on table openning, then that will be
great news, since the only thing you should do is make a call to that
function before openning any table. BTW, if that internal flag is used by
the the ADS system continously then there is nothing to do.
I suposse is the first case. If you could confirm it, I may be able to
modifiy the class so the function is called every time a dataset is going to
be openned.
Regards,
"Aguiar" <aguiar.costa@sisbit.pt> escribió en el mensaje
news:45783807$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Ignacio,
>
> What Paulo is saying is that we did some tests and it seems that having 2
> Datasources 1 set to Ansi and other set to OEM (defined at IDE level), the
> set that stays active is the one of the second Datasource...But if you do
> the same at code level it works....can you confirm this ?
> Thanks.
> Aguiar !!!
>
>
> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
> news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
>> Paulo,
>>
>> I believe there is no solution for that problem because xHarbour
>> ADSSetChartype() function sets that value for the complete application.
>> It does not recognize multiple connections on the same app. You may post
>> this problem in xHarbour forum and ask if is possible that this functions
>> accepts a new parameter indicanting the connection handle.
>>
>> Regards,
>>
>> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
>> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>> Hi, i have two oAdsDataSource defined in IDE.
>>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>>> The problem is that all oDbfDataSet stay with the property of the last.
>>> I only resolve this, put after all oDbfDataSet:Open() the property
>>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>>> Why this property only work if defined in the code?
>>>
>>>
>>> Regards.
>>>
>>
>>
>>
>
>
>

TAdsDataSource.

Publicado: Lun Dic 11, 2006 12:10 pm
por pjmfelix
Ignacio,
If i have this in the code, it works !
::oDBFDataSet1:oDataSource := ::oParent:oAdsDataSource1
::oDBFDataSet1:oDataSource:nCharType := 1
::oDBFDataSet1:Open()
::oDBFDataSet2:oDataSource := ::oParent:oAdsDataSource2
::oDBFDataSet2:oDataSource:nCharType := 2
::oDBFDataSet2:Open()
Now, if i have the nCharType define in the oAdsDataSource, don´t work.
All the tables stay with the nCharType of the last oAdsDataSource Defined.
Regards.
"Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
news:[email=4579293a@news.xailer.com...]4579293a@news.xailer.com...[/email]
> Aguiar,
>
> I am not sure how it works the function ADSSetCharType(). If the function
> sets a internal flag that ONLY is used on table openning, then that will
> be great news, since the only thing you should do is make a call to that
> function before openning any table. BTW, if that internal flag is used by
> the the ADS system continously then there is nothing to do.
>
> I suposse is the first case. If you could confirm it, I may be able to
> modifiy the class so the function is called every time a dataset is going
> to be openned.
>
> Regards,
>
>
> "Aguiar" <aguiar.costa@sisbit.pt> escribió en el mensaje
> news:45783807$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>> Ignacio,
>>
>> What Paulo is saying is that we did some tests and it seems that having 2
>> Datasources 1 set to Ansi and other set to OEM (defined at IDE level),
>> the set that stays active is the one of the second Datasource...But if
>> you do the same at code level it works....can you confirm this ?
>> Thanks.
>> Aguiar !!!
>>
>>
>> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
>> news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
>>> Paulo,
>>>
>>> I believe there is no solution for that problem because xHarbour
>>> ADSSetChartype() function sets that value for the complete application.
>>> It does not recognize multiple connections on the same app. You may post
>>> this problem in xHarbour forum and ask if is possible that this
>>> functions accepts a new parameter indicanting the connection handle.
>>>
>>> Regards,
>>>
>>> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
>>> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>>> Hi, i have two oAdsDataSource defined in IDE.
>>>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>>>> The problem is that all oDbfDataSet stay with the property of the last.
>>>> I only resolve this, put after all oDbfDataSet:Open() the property
>>>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>>>> Why this property only work if defined in the code?
>>>>
>>>>
>>>> Regards.
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>

TAdsDataSource.

Publicado: Lun Dic 11, 2006 12:10 pm
por pjmfelix
Ignacio,
If i have this in the code, it works !
::oDBFDataSet1:oDataSource := ::oParent:oAdsDataSource1
::oDBFDataSet1:oDataSource:nCharType := 1
::oDBFDataSet1:Open()
::oDBFDataSet2:oDataSource := ::oParent:oAdsDataSource2
::oDBFDataSet2:oDataSource:nCharType := 2
::oDBFDataSet2:Open()
Now, if i have the nCharType define in the oAdsDataSource, don´t work.
All the tables stay with the nCharType of the last oAdsDataSource Defined.
Regards.
"Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
news:[email=4579293a@news.xailer.com...]4579293a@news.xailer.com...[/email]
> Aguiar,
>
> I am not sure how it works the function ADSSetCharType(). If the function
> sets a internal flag that ONLY is used on table openning, then that will
> be great news, since the only thing you should do is make a call to that
> function before openning any table. BTW, if that internal flag is used by
> the the ADS system continously then there is nothing to do.
>
> I suposse is the first case. If you could confirm it, I may be able to
> modifiy the class so the function is called every time a dataset is going
> to be openned.
>
> Regards,
>
>
> "Aguiar" <aguiar.costa@sisbit.pt> escribió en el mensaje
> news:45783807$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>> Ignacio,
>>
>> What Paulo is saying is that we did some tests and it seems that having 2
>> Datasources 1 set to Ansi and other set to OEM (defined at IDE level),
>> the set that stays active is the one of the second Datasource...But if
>> you do the same at code level it works....can you confirm this ?
>> Thanks.
>> Aguiar !!!
>>
>>
>> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
>> news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
>>> Paulo,
>>>
>>> I believe there is no solution for that problem because xHarbour
>>> ADSSetChartype() function sets that value for the complete application.
>>> It does not recognize multiple connections on the same app. You may post
>>> this problem in xHarbour forum and ask if is possible that this
>>> functions accepts a new parameter indicanting the connection handle.
>>>
>>> Regards,
>>>
>>> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
>>> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>>> Hi, i have two oAdsDataSource defined in IDE.
>>>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>>>> The problem is that all oDbfDataSet stay with the property of the last.
>>>> I only resolve this, put after all oDbfDataSet:Open() the property
>>>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>>>> Why this property only work if defined in the code?
>>>>
>>>>
>>>> Regards.
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>

TAdsDataSource.

Publicado: Lun Dic 11, 2006 8:17 pm
por ignacio
Paulo,
Fixed. It will be available on next release.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
news:457d43fd$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Ignacio,
>
> If i have this in the code, it works !
>
> ::oDBFDataSet1:oDataSource := ::oParent:oAdsDataSource1
> ::oDBFDataSet1:oDataSource:nCharType := 1
> ::oDBFDataSet1:Open()
> ::oDBFDataSet2:oDataSource := ::oParent:oAdsDataSource2
> ::oDBFDataSet2:oDataSource:nCharType := 2
> ::oDBFDataSet2:Open()
>
> Now, if i have the nCharType define in the oAdsDataSource, don´t work.
> All the tables stay with the nCharType of the last oAdsDataSource Defined.
>
> Regards.
>
>
>
>
> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
> news:[email=4579293a@news.xailer.com...]4579293a@news.xailer.com...[/email]
>> Aguiar,
>>
>> I am not sure how it works the function ADSSetCharType(). If the function
>> sets a internal flag that ONLY is used on table openning, then that will
>> be great news, since the only thing you should do is make a call to that
>> function before openning any table. BTW, if that internal flag is used by
>> the the ADS system continously then there is nothing to do.
>>
>> I suposse is the first case. If you could confirm it, I may be able to
>> modifiy the class so the function is called every time a dataset is going
>> to be openned.
>>
>> Regards,
>>
>>
>> "Aguiar" <aguiar.costa@sisbit.pt> escribió en el mensaje
>> news:45783807$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>> Ignacio,
>>>
>>> What Paulo is saying is that we did some tests and it seems that having
>>> 2 Datasources 1 set to Ansi and other set to OEM (defined at IDE level),
>>> the set that stays active is the one of the second Datasource...But if
>>> you do the same at code level it works....can you confirm this ?
>>> Thanks.
>>> Aguiar !!!
>>>
>>>
>>> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
>>> news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
>>>> Paulo,
>>>>
>>>> I believe there is no solution for that problem because xHarbour
>>>> ADSSetChartype() function sets that value for the complete application.
>>>> It does not recognize multiple connections on the same app. You may
>>>> post this problem in xHarbour forum and ask if is possible that this
>>>> functions accepts a new parameter indicanting the connection handle.
>>>>
>>>> Regards,
>>>>
>>>> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
>>>> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>>>> Hi, i have two oAdsDataSource defined in IDE.
>>>>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>>>>> The problem is that all oDbfDataSet stay with the property of the
>>>>> last.
>>>>> I only resolve this, put after all oDbfDataSet:Open() the property
>>>>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>>>>> Why this property only work if defined in the code?
>>>>>
>>>>>
>>>>> Regards.
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>

TAdsDataSource.

Publicado: Lun Dic 11, 2006 8:17 pm
por NoName
Paulo,
Fixed. It will be available on next release.
Regards,
--
Ignacio Ortiz de Zúñiga
http://www.xailer.com
"Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
news:457d43fd$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> Ignacio,
>
> If i have this in the code, it works !
>
> ::oDBFDataSet1:oDataSource := ::oParent:oAdsDataSource1
> ::oDBFDataSet1:oDataSource:nCharType := 1
> ::oDBFDataSet1:Open()
> ::oDBFDataSet2:oDataSource := ::oParent:oAdsDataSource2
> ::oDBFDataSet2:oDataSource:nCharType := 2
> ::oDBFDataSet2:Open()
>
> Now, if i have the nCharType define in the oAdsDataSource, don´t work.
> All the tables stay with the nCharType of the last oAdsDataSource Defined.
>
> Regards.
>
>
>
>
> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
> news:[email=4579293a@news.xailer.com...]4579293a@news.xailer.com...[/email]
>> Aguiar,
>>
>> I am not sure how it works the function ADSSetCharType(). If the function
>> sets a internal flag that ONLY is used on table openning, then that will
>> be great news, since the only thing you should do is make a call to that
>> function before openning any table. BTW, if that internal flag is used by
>> the the ADS system continously then there is nothing to do.
>>
>> I suposse is the first case. If you could confirm it, I may be able to
>> modifiy the class so the function is called every time a dataset is going
>> to be openned.
>>
>> Regards,
>>
>>
>> "Aguiar" <aguiar.costa@sisbit.pt> escribió en el mensaje
>> news:45783807$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>> Ignacio,
>>>
>>> What Paulo is saying is that we did some tests and it seems that having
>>> 2 Datasources 1 set to Ansi and other set to OEM (defined at IDE level),
>>> the set that stays active is the one of the second Datasource...But if
>>> you do the same at code level it works....can you confirm this ?
>>> Thanks.
>>> Aguiar !!!
>>>
>>>
>>> "Ignacio Ortiz de Zúñiga" <_support_@xailer.com> escreveu na mensagem
>>> news:[email=45782e71@news.xailer.com...]45782e71@news.xailer.com...[/email]
>>>> Paulo,
>>>>
>>>> I believe there is no solution for that problem because xHarbour
>>>> ADSSetChartype() function sets that value for the complete application.
>>>> It does not recognize multiple connections on the same app. You may
>>>> post this problem in xHarbour forum and ask if is possible that this
>>>> functions accepts a new parameter indicanting the connection handle.
>>>>
>>>> Regards,
>>>>
>>>> "Paulo Jorge M. Félix" <pjmfelix@sisbit.pt> escribió en el mensaje
>>>> news:457824b5$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
>>>>> Hi, i have two oAdsDataSource defined in IDE.
>>>>> One for use nCharType = acANSI, and the other for nCharType = acOEM.
>>>>> The problem is that all oDbfDataSet stay with the property of the
>>>>> last.
>>>>> I only resolve this, put after all oDbfDataSet:Open() the property
>>>>> oDBFDataSet:oDataSource:nCharType := 1 or 2.
>>>>> Why this property only work if defined in the code?
>>>>>
>>>>>
>>>>> Regards.
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>