Re: BDE -> ADO

From: "Bill Todd" <no@xxxxxx>
Date: 12 Jun 2006 19:49:18 -0700

Hannes Danzl[NDD] wrote:

If your product is currently table based and you've not taken
precautions for later switching to query based, you'll very likely be
in for a big nasty surprise in terms of performance. Writing SQL
based software is a complete different thing compared to table based
approaches.

He is already using SQL Server 2000 with the BDE and TTables so move to
ADO with TADOTable may not degrade performance.

--
Bill Todd (TeamB)
.

Follow-Ups:
- Re: BDE -> ADO
  - From: Hannes Danzl[NDD]

References:
- BDE -> ADO
  - From: keith
- Re: BDE -> ADO
  - From: Bill Todd
- Re: BDE -> ADO
  - From: keith
- Re: BDE -> ADO
  - From: Hannes Danzl[NDD]

Prev by Date: FieldByName('Latitude').Text; --- It is truncating the value
Next by Date: Re: BDE -> ADO
Previous by thread: Re: BDE -> ADO
Next by thread: Re: BDE -> ADO
Index(es):
- Date
- Thread

Relevant Pages

Re: BDE -> ADO
... precautions for later switching to query based, ... in for a big nasty surprise in terms of performance. ... Writing SQL ... ADO with TADOTable may not degrade performance. ...
(borland.public.delphi.database.ado)
Re: Set parameters for nested query
... there are easy work arounds by saving the query or ... writing SQL into the code. ... means more query tedium. ...
(comp.databases.ms-access)
Re: Parameter Driven Query
... MS Query is set up to use parameters easily - you can use square ... advanced interface) for the criteria values. ... the query Excel will display a dialog where you can choose to use a ... ui is just writing SQL based on your input anyhow) ...
(microsoft.public.excel.programming)