There is a major problem here with DataGrid binding and that is of cursor
resources.
They like fully scrollable cursors and are real hoggers.
One thing I do for client side is use a listview set lvreport.
open a recordset
rs.cusorlocation = aduseclient
rs.cusrortype = adstatic
rs.locktype = adbatchupdate
rs.open sql, myconn
then rs.activeconnection = nothing
myconn .close

this disconnects the recordset.
Then you can manipulate the list view from the recordset by setting all the
parameters from the recordset properties
Also one thing is that you often don't want to see the primary key
when the user makes a change get the tag value (primary key)
manipulate the recordset.
when you have finnished you need to resync
so myconn.open
rs.activeconnection = myconn
rs.updatebatch

you need to enter a error handling routine for concurrency issuses.

rs.close
myconn.close
do the nothings and go

-----Original Message-----
From: Rainer Park [mailto:Rainer@C...]
Sent: 16 February 2001 19:46
To: professional vb
Subject: [pro_vb] Re: Questions on DataGrid


Peter: there are a number of grids out there

MSFlexGrid
Apex TrueDb Grid
Janus Grid


The grids usually have some type of property such as
grid.recordsource=ado recordset.

It' pretty straight forward. I did not like the grids that come with VB6.


Hope this helps.