Thanks Jim. Now it is realy more clearer. Cursoradapter is my favourite new feature of VFP8 - so I really appreciate your help. I am with fox since FPD 2.0 but I am quite new as regard as working in client-server environment.
The cursoradapter class realy help me to enter the new world more quickly.
That's pity that very good impresion of cursoradapter class is partially spoiled by problems with saving into property sheet cursorschema strings longer then 255 chars and lack of DE and CA builders in report dataenvironment. But again - despite above mentioned things - cursoradapters are great idea IMHO. Good luck.

>
>In VFP7 and prior, the ODBC connection (ODBChdbc) and ODBC statement (ODBChstmt) handles were always the same for a given VFP connection. Sharing statement handles can cause problems.
>
>VFP8 now allows you to have multiple ODBC statement handles for a given ODBC connection. This allows a single server connection, yet lets you avoid problems associated with using a single ODBC statement handle for multiple views or cursoradapters. In prior versions, using unique ODBC statement handles always required unique ODBC connection handles, and consequently unique ODBC connections to the back end server.
>
>So in VFP7 and prior, a unique VFP connection handle (the integer returned by the SQLConnect(), for example), always corresponded to a unique ODBC statement and ODBC connection handle. In VFP8, a unique VFP connection handle corresponds to a unique ODBC statement handle, which may or may not be a unique ODBC connection handle.
>
>I hope this makes things a little clearer.


>> And found no reason. ODBChdbc is always the same, ODBChstmt have always different values. What I am missing ? Would you be so kind and explain your idea ?