Re: Conversion from BDE to ADO
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 03/25/04
- Next message: Vitali Kalinin: "Re: About TDatasetField in TADODataset"
- Previous message: Brian Bushay TeamB: "Re: A compact problem"
- In reply to: John Faris: "Conversion from BDE to ADO"
- Next in thread: eWolverine: "Re: Conversion from BDE to ADO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 24 Mar 2004 23:01:37 -0600
>I am currently experimenting with converting a quite large app from BDE to
>ADO. It accesses a MS SQL 2000 database, and before I commit and jump
>headlong into this I wonder if there are any major issues to be aware of?
>One of the main benefits I am hoping for is better multi-user detection
>capabillity e.g. if one user changes a record another has open and then the
>other user tries to change they get an appropriate error message.
They will get an error message that the record was changed by another user
> I have
>found BDE support for this a little flakey at best. Are there any setting
>changes from the default on TAdoQuery or TAdoConnection that I should
>definitely make? Finally I have seen a fair bit of discussion around
>suggesting that ADO will slow my app down, is this true?
That depends on how you programmed your application. If you just opened Ttables
to display all records from a large table and you continue this practice in a
conversion you will get a poorer preforming application.
Ado Client side cursors load all records into memory and will be slower if you
open datasets with a lot of records.
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Next message: Vitali Kalinin: "Re: About TDatasetField in TADODataset"
- Previous message: Brian Bushay TeamB: "Re: A compact problem"
- In reply to: John Faris: "Conversion from BDE to ADO"
- Next in thread: eWolverine: "Re: Conversion from BDE to ADO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|