Thread View: borland.public.cppbuilder.database.ado
6 messages
6 total messages
Started by John Scott
Wed, 23 Mar 2005 21:52
Access 2K and ADO slow
Author: John Scott
Date: Wed, 23 Mar 2005 21:52
Date: Wed, 23 Mar 2005 21:52
6 lines
1298 bytes
1298 bytes
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
Re: Access 2K and ADO slow
Author: Arnie
Date: Thu, 24 Mar 2005 20:02
Date: Thu, 24 Mar 2005 20:02
15 lines
1470 bytes
1470 bytes
"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
Re: Access 2K and ADO slow
Author: Viatcheslav V. Vassiliev
Date: Fri, 25 Mar 2005 10:50
Date: Fri, 25 Mar 2005 10:50
29 lines
2324 bytes
2324 bytes
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 >
Re: Access 2K and ADO slow
Author: John Scott
Date: Fri, 25 Mar 2005 17:11
Date: Fri, 25 Mar 2005 17:11
42 lines
2748 bytes
2748 bytes
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 >> > >
Re: Access 2K and ADO slow
Author: 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 > >> > > > > >
Re: Access 2K and ADO slow
Author: 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 >> >> >> > >> > >> > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads