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.

Execute method in tadodatasource

Xailer English public forum
Responder
Guest

Execute method in tadodatasource

Mensaje por Guest »

Should Xailer's implementation of the the ADO Execute method, be able to
execute SELECTs?
For example,
This returns the expected data, in an arry:
aSQLReturnedRows := ::oSQLServerADODS:QueryArray( "SELECT * FROM
ETL.PEOPLE" )
, and this returns a true, but the dataset oSQLServerDataSet is nil:
xResult := ::oSQLServerADODS:Execute( "SELECT * FROM ETL.PEOPLE", , ,
@oSQLServerDataSet )
Yes, I understand that the Query() method is a better way to return
results of SELECTs, but I'm just trying to figure out how to use
Execute() in general.
DC
Mensajes: 135
Registrado: Lun May 16, 2011 6:06 pm

Execute method in tadodatasource

Mensaje por DC »

Does anyone have any information about this?
On 6/28/2011 10:52 AM, DC wrote:
> Should Xailer's implementation of the the ADO Execute method, be able to
> execute SELECTs?
>
> For example,
>
> This returns the expected data, in an arry:
>
> aSQLReturnedRows := ::oSQLServerADODS:QueryArray( "SELECT * FROM
> ETL.PEOPLE" )
>
>
> , and this returns a true, but the dataset oSQLServerDataSet is nil:
>
> xResult := ::oSQLServerADODS:Execute( "SELECT * FROM ETL.PEOPLE", , ,
> @oSQLServerDataSet )
>
>
>
> Yes, I understand that the Query() method is a better way to return
> results of SELECTs, but I'm just trying to figure out how to use
> Execute() in general.
>
>
Avatar de Usuario
ignacio
Site Admin
Mensajes: 9447
Registrado: Lun Abr 06, 2015 8:00 pm
Ubicación: Madrid, Spain
Contactar:

Execute method in tadodatasource

Mensaje por ignacio »

Childers escribió el mar, 28 junio 2011 16:52Should Xailer's implementation of the the ADO Execute method, be able to
execute SELECTs?
For example,
This returns the expected data, in an arry:
aSQLReturnedRows := ::oSQLServerADODS:QueryArray( "SELECT * FROM
ETL.PEOPLE" )
, and this returns a true, but the dataset oSQLServerDataSet is nil:
xResult := ::oSQLServerADODS:Execute( "SELECT * FROM ETL.PEOPLE", , ,
@oSQLServerDataSet )
Yes, I understand that the Query() method is a better way to return
results of SELECTs, but I'm just trying to figure out how to use
Execute() in general.
The third parameter nOptions should be set to adCmdText (1) in order to let ADO connection return a record set. BTW, It will be the default value on next release.
Regards,
Ignacio Ortiz de Zúñiga
[OZ Software]
https://www.ozs.es
--
[Equipo de Xailer / Xailer team]
https://www.xailer.com
DC
Mensajes: 135
Registrado: Lun May 16, 2011 6:06 pm

Execute method in tadodatasource

Mensaje por DC »

Yep, that's it, thanks Ignacio.
On 6/30/2011 3:57 AM, Ignacio Ortiz de Zúñiga wrote:
> Childers escribió el mar, 28 junio 2011 16:52
>> Should Xailer's implementation of the the ADO Execute
>> method, be able to execute SELECTs?
>>
>> For example,
>>
>> This returns the expected data, in an arry:
>>
>> aSQLReturnedRows := ::oSQLServerADODS:QueryArray(
>> "SELECT * FROM ETL.PEOPLE" )
>>
>>
>> , and this returns a true, but the dataset
>> oSQLServerDataSet is nil:
>>
>> xResult := ::oSQLServerADODS:Execute( "SELECT * FROM
>> ETL.PEOPLE", , , @oSQLServerDataSet )
>>
>>
>>
>> Yes, I understand that the Query() method is a better
>> way to return results of SELECTs, but I'm just trying to figure out
>> how to use Execute() in general.
>
>
> The third parameter nOptions should be set to adCmdText (1)
> in order to let ADO connection return a record set. BTW, It
> will be the default value on next release.
>
> Regards,
Responder