Article View: borland.public.cppbuilder.database.ado
Article #744Re: Access 2K and ADO slow
From: Daniel Stevenson
Date: Tue, 29 Mar 2005 01:48
Date: Tue, 29 Mar 2005 01:48
56 lines
3185 bytes
3185 bytes
You may also get some speed increases by using TADOTable1->DisableControls(); prior to stepping through the records in your table. DisableControls(); also works for TADOQuery and I'm not sure about TADODataset as I don't use that too often. if you have data-aware controls that are linked to these tables/queries than you should ->EnableControls(); once you are finished playing with the table/query. "John Scott" <jscott@kw.igs.net> wrote in message news:42444646@newsgroups.borland.com... > Thanks: Yes I found that out that this is the only choice that allows > indexes and seeks. The application was first developed using the BDE > with Access 97. > I think I have found that the slow responce is due to many lookup and > calculated fields. > > John > "Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote in message > news:4243ecf7$1@newsgroups.borland.com... > > TADOTable with server-side cursor and TableDirect = true is very > > effective for MS Access. This is only one configuration that allows > > use of indexes and Seek(). > > > > //------------------------------------------ > > Regards, > > Vassiliev V. V. > > http://www.managed-vcl.com - using .Net objects in Delphi for Win32 > > + ADO.Net > > http://www.oledbdirect.com - The fastest way to access MS SQL > > Server, > > MS Jet (Access) and Interbase (through OLEDB) > > > > "Arnie" <none> �������/�������� � �������� ���������: > > news:42431ce8$1@newsgroups.borland.com... > >> "John Scott" <jscott@kw.igs.net> wrote in message > >> news:4241e517$1@newsgroups.borland.com... > >>> My appliction uses ADO with and Access 2K database. I mostly use > >>> tables and indexes - to order the data. I find that seeks and > >>> other database actions are slow. Are there any parameters that I > >>> can modify that might speed it up? > >>> > >>> John > >> > >> A little more info would be helpful. If you're using TADOTable, > >> don't. Use either the TADODataset or TADOQuery objects and use the > >> SQL statement with a WHERE clause to filter your result and an > >> ORDER BY to order it. > >> > >> - Arnie > >> > > > > >
Technical Details
Message-ID:
<4248b3ca@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!gatel-ffm!gatel-ffm!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<4241e517$1@newsgroups.borland.com> <42431ce8$1@newsgroups.borland.com> <4243ecf7$1@newsgroups.borland.com> <42444646@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10698b,1f7459b1c2069d5f X-Google-Attributes: gid10698b,public X-Google-Language: ENGLISH,ASCII From: "Daniel Stevenson" <d.stevenson@ocreage.com.au> Newsgroups: borland.public.cppbuilder.database.ado References: <4241e517$1@newsgroups.borland.com> <42431ce8$1@newsgroups.borland.com> <4243ecf7$1@newsgroups.borland.com> <42444646@newsgroups.borland.com> Subject: Re: Access 2K and ADO slow Date: Tue, 29 Mar 2005 11:48:08 +1000 Lines: 58 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 NNTP-Posting-Host: 202.174.233.53 Message-ID: <4248b3ca@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1112060874 202.174.233.53 (28 Mar 2005 17:47:54 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!gatel-ffm!gatel-ffm!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail