Hi guys,

Is there any kind of restriction as to the data types and method types exportable through datasnap? I have been using datasnap for quite sometimes. But usually export datasets, and manipulate them on client side, and save changes to server by way of Tdatasetproviders exposed by datasnap. I wanted to take advantage of using scalar functions, and procedures I could control on the server side, avoiding the obligation to deploy a new client every time we make achange. But I noticed that functions returning ex
tended type, boolean and integer types, and the procedures are not visible to the client. Am I missing something? Please, help. TIA.

Emmanuel

> {quote:title=Emmanuel Lamy wrote:}{quote}
> Hi guys,
> 
> Is there any kind of restriction as to the data types and method types exportable through datasnap? I have been using datasnap for quite sometimes. But usually export datasets, and manipulate them on client side, and save changes to server by way of Tdatasetproviders exposed by datasnap. I wanted to take advantage of using scalar functions, and procedures I could control on the server side, avoiding the obligation to deploy a new client every time we make achange. But I noticed that functions returning 
extended type, boolean and integer types, and the procedures are not visible to the client. Am I missing something? Please, help. TIA.
> 
> Emmanuel

Just want to share the answer here in case others were interested. I was able to create and expose scalar functions returning all the common types, and non-returning procedures when using the FireDac DB Framework with D XE5 Ultimate. Thanks.

Emmanuel