Re: Delphi6. ADO <->SQLExpress - best practice?
- From: "Del Murray" <Del.Murray@xxxxxxxxxxxxxx>
- Date: Tue, 8 Jan 2008 08:15:34 -0600
Pat,
See this for details.
http://technet.microsoft.com/en-us/library/ms345154.aspx
Unlike BDE and Paradox, dont use tADOTable .. it will open th whole table
which can kill you. Use tADODataset to read only the data needed for the
application. If your UI is based on a primary "browse", as many are, you
will have to change that to work with a more finite number of records at a
time.
With a 1 GB buffer memory limit, i would steer away from stored procs if you
can .. although I admit that this is just a guess on my part, but probably
close to the mark.
If you use ADO recordsets, you can edit directly to the recordset. The data
can then be committed to the database "optimistically" (as it is changed),
or batchoptimistically, (changes are buffered for all records in a record
set and then committed to the database with the UpdateBatch method of
tADODataset). Just depends on the requirements of the app. Batch updating is
helpful when you have multiple reords being created and dont want to commit
to DB until all is ok .. as in a "new invoice" with multiple line items and
then the user decides .. "Oh hell, that's the wrong customer" .. You havent
done anything to the database so you can just do "cancel updates" and the
new recs disappear from the recordset.
HTH,
Del
.
- Follow-Ups:
- Re: Delphi6. ADO <->SQLExpress - best practice?
- From: P . S . Bell
- Re: Delphi6. ADO <->SQLExpress - best practice?
- Prev by Date: Re: Delphi6. ADO <->SQLExpress - best practice?
- Next by Date: EOLEException error "Row Handle referred to a deleted row or row marked for deletion" with CancelBatch
- Previous by thread: Re: Delphi6. ADO <->SQLExpress - best practice?
- Next by thread: Re: Delphi6. ADO <->SQLExpress - best practice?
- Index(es):
Relevant Pages
|
|
