🚀 go-pugleaf

> Hi, Piero!
>

Hi, Mark!

> If you are using SQL Server you do not need to worry too much about
> concurrent access because that will be handled in the client-server
> DBMS.

Sorry, but I don't think so. If you let the DB act without issuing Begin-End
Transactions you might run into consistency problems...

From what I saw looking around the ADO (and BDE) components I made up the
idea that I should use Client Side Cursors, Batch Updates and an explicit
Transaction control to achieve the goals.
But I saw also that with client cursors you get all the record fetched into
the client, with loss of performance for huge tables (I got not so huge
tables, but anyway 40.000 records are too much to be fetched efery time) .

Any trick?
And, are there some ways to get the records on a DBgrid refreshed wirthout
barely requerying everything?

Thanks in advance.

> If you use Access, nothing you do can absolutely ensure safety.

Is there a way to simulate a Transaction on the client side?

> If you'd like to use the transaction features of the TADOConnection
> object, have a look at BeginTrans(), EndTrans(), Commit() and Abort().
> There are a variety of transaction isolation levels available.
>
> The data set should have its MarshalOptions set to moModfiedOnly to
> reduce traffic over the network.

I'll try.
'Bout the book, seems like there are thiusands of pages I do not mind by
now. Bu that is the problem of EVERY book I bought since the last 4 years.
Somedthing thinner like "Using ADO on relational DBMS"?

Thanks anyway


--
Ing. Piero Salandin
piero.salandin@libero.it