Hi,
In disconnected environment you could add and change records in recordset,
since you do not have any access to the actual database. It works fast and
allows you manipulate data without supporting active connection. Benefits of
using disconnected recordset are; you do not hold resources of database,
everything works fast, because it is local. Possible drawbacks: When you
need to open disconnected recordset, then you have to open it on client
side. In case of big number of records it could take some time to transfer
all those records to client side. If you decide to update changes from
recordset to database, then it could take some time as well, but you could
test performance in your particular case using some sort of test application
--
Val Mazur
Microsoft MVP
Quote:
> Thanx Val.
> But then when should we use Recordset.addnew/recordset.update.
> And also are there any benifits/drawbacks of using disconnected recordsets
> in a purely Client/Server Architecture.
> > Hi,
> > In case of transaction (and not only) I would suggest to use explicit
SQL
> > statements, instead of working with ADO recordset. In some cases
> > transactions are failing when you work through recordsets
> > --
> > Val Mazur
> > Microsoft MVP
> > > hi,
> > > I would like to know which is a better Recordset.Addnew and
> > > recordset.update or
> > > Building an INSERT statement and
> > > using connection.execute "Insert Statment"
> > > for a Transaction Processing System.
> > > Thanx in Advance.
> > > And also for a Transaction Processing System (Purely Client/Server)
> should
> > a
> > > disconneted recordset be used.
Recorset.addnew/INSERT