Re: Any reason why accessing Access should slowdown?
- From: JohnBury <JohnBury@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 Oct 2006 08:20:02 -0700
Paul
The database is on the same machine as the VB application.
On the MSACCESS / JET OLEDB front, you responded to a query I had about the
problems I was having with JET, but I never really resolved the issue.
To remind you, when I repolaced my connection string so that it used JET, my
application stopped being able to display filtered data in datagrids.
If you wish to continue thie dialogue on this issue then...
This is what I did
At design time...
Declared connection to Access database using string based on Jet OLDB
provider.
Created an ADODC on my form with datagrid.
Used ADODC to initially load columns to allow me to format grid
removed reference to ADODC from grid's datasource property
At runtime
during Form Load
Set up recordset filter in response to earlier input / selection
Set datagrid datasource property to recordset
What happens? Nothing! I can display recordcount of filtered recordset in
the immediate window, but datgrid refuses to display records.
Swap connection back to use MSACCESS provider and it works fine!
My recordsets are opened as 'adKeySet'
Cursors are all client side
If you have any ideas I would welcome them!
Cheers!
John
--
UK John
"Paul Clement" wrote:
On Sun, 1 Oct 2006 02:21:02 -0700, JohnBury <JohnBury@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
¤ I am writing a VB6 App using an Access database backend (not clever but cheap!)
¤
¤ Yesterday the performance of data access became unacceptably slow, from near
¤ instantaneous to 10 seconds to retrieve 4 records to fill a datagrid.
¤
¤ It happened after I had added a new table to fill a combo box with default
¤ values. I 'regressed (removing new code and references to the new table, but
¤ performance as still poor. Something like this has happened before and was
¤ fixed by a database repair, but not this time!
¤
¤ Any ideas where I should look for my problem?
¤
This database isn't located on a network resource is it?
I typically don't recommend using the Microsoft Access ODBC driver since it isn't as stable as the
Jet OLEDB Provider.
Paul
~~~~
Microsoft MVP (Visual Basic)
- Follow-Ups:
- Re: Any reason why accessing Access should slowdown?
- From: Paul Clement
- Re: Any reason why accessing Access should slowdown?
- From: Paul Clement
- Re: Any reason why accessing Access should slowdown?
- References:
- Re: Any reason why accessing Access should slowdown?
- From: Paul Clement
- Re: Any reason why accessing Access should slowdown?
- Prev by Date: Re: table export from local Access to import in remote Access database in VB
- Next by Date: Re: Querying a database
- Previous by thread: Re: Any reason why accessing Access should slowdown?
- Next by thread: Re: Any reason why accessing Access should slowdown?
- Index(es):
Relevant Pages
|
