Hi All,

I was wondering if anyone could offer me any advice.

I have written an application, which has made extanisve use of
dyanset's when linking to an Access 2.0 database over a Novell
Network.

One part of the program needs to do a considerable number of updates
to one of the tables.

I have noticed that the performance of this part of the application
was pathetic. I had tried all the freelock, tricks, but to no avail.

On impulse I changes the code to open the table using a table as
opposed to a dynaset.

This has had a massive improvement over the performace.

Does anyone know why this is, and could I encounter any problems on a
multiuser system using this different approach.

On a more general course, are there any guidelines VB guru's out there
can provide as to when to use Dynaset's or Tablesets. Of course I
assume the Snapshot is used when you wish to find something quickly or
build pick lists etc.

Any help would be appreciated.

Cheers

Russ
R & L Enterprises - Software/ Hardware Development & Distribution
M.L. Greenwood's & Associates - Business & Technical Consultancy

  A snapshot is "as the name implies" a picture of the data.  A copy of
the data is used to create the recordset.  This recordset should be used
in a read only situation.  It takes more time to create but is faster
than a dynaset to access.  

  A dynaset is used when your data source consist of a "Sql statement".
This recordset is updateable in most situations.  

  A tabledef is the fastest method.  The relation is opened directly
with this method.  It also makes use of indexed lookups.  The previous
methods make use of the "locate" method for searching which are slower.  

                                                        Allen

In theory, Dynasets make that only the key fields of the table records
were in memory when you're processing records. Tables keep all the
information in memory, not only the key fields. But, in practice,
reality seems different. I think it's due to a different implementation
of table objects, cause that kind of recordset can only work with one
table ( in database ), and this causes that all the extra code that have
the Dynaset, which can access more than one, to be eliminated. We can
say that is a lighter object.

My experience has shown me that tables are faster because they are
objects with easyer methods than Dynasets, which can process more
complex methods.

By the way, is possible that Dynasets cause more record, even table,
locks than tables.

Bye.

Juanma.