Re: BDE vs ADO
From: Jeremy Collins (jd.collins_at_ntlworld-not.com)
Date: 02/27/04
- Next message: Jeremy Collins: "Re: BDE vs ADO"
- Previous message: Denis Jeanroy: "Re: Run external application from within Delphi"
- In reply to: Christian Charest: "Re: BDE vs ADO"
- Next in thread: Toon Krijthe: "Re: BDE vs ADO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Feb 2004 08:44:16 +0000
Christian Charest wrote:
> I'm working with an access database with a lot of stored procedurs.
Then it's probably a good idea to switch to ADO. The ADO
datasets have very similar methods to the BDE equivalent,
and they still connect to the same data-aware components
via TDataSource, so the transition shouldn't be too hard.
I recommend you you TADODataSet, rather than TADOTable,
since this will make your life much easier if your app
gets upgraded to SQL Server or similar. The TADODataSet
can also return a recordset from a stored procedure,
and if you have SPs that INSERT, UPDATE or similar then
you can use TADOCommand or TADOStoredProc.
I assume you're using a TDataModule already; if not this
is a good time to start. Drop a TADOConnection on your data
module, and build the connection string; it will be something
like
Provider=Microsoft.Jet.OLEDB.4.0;
Data Source=c:\YourDB.mdb;
Persist Security Info=False
You then set your TADODataSet's Connection propery to this
connection object.
You might also want to start reading the
borland.public.delphi.database.ado newsgroup.
HTH
-- jc Remove the -not from email
- Next message: Jeremy Collins: "Re: BDE vs ADO"
- Previous message: Denis Jeanroy: "Re: Run external application from within Delphi"
- In reply to: Christian Charest: "Re: BDE vs ADO"
- Next in thread: Toon Krijthe: "Re: BDE vs ADO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|