Article View: borland.public.cppbuilder.database.ado
Article #747Re: Access 2K and ADO slow
From: John Scott
Date: Wed, 30 Mar 2005 01:08
Date: Wed, 30 Mar 2005 01:08
75 lines
3615 bytes
3615 bytes
Thank you I will try that out John "Daniel Stevenson" <d.stevenson@ocreage.com.au> wrote in message news:4248b3ca@newsgroups.borland.com... > 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:
<4249fc09@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!newshub.sdsu.edu!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!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> <4248b3ca@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: "John Scott" <jscott@kw.igs.net> 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> <4248b3ca@newsgroups.borland.com> Subject: Re: Access 2K and ADO slow Date: Tue, 29 Mar 2005 20:08:22 -0500 Lines: 76 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 NNTP-Posting-Host: 216.16.227.141 Message-ID: <4249fc09@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1112144905 216.16.227.141 (29 Mar 2005 17:08:25 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!newshub.sdsu.edu!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail