Re: Any reason why accessing Access should slowdown?
- From: Paul Clement <UseAdddressAtEndofMessage@xxxxxxxxxxxxxx>
- Date: Wed, 04 Oct 2006 11:42:03 -0500
On Mon, 2 Oct 2006 08:20:02 -0700, JohnBury <JohnBury@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I just tried the following simple example and it worked for me. Initially the DataGrid is not bound
to a Data Control. It worked fine for all of the CursorTypes. The CursorLocation must be
client-side. The Requery method is not required.
cnn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=C:\Test Files\db1 XP.mdb;" & _
"Jet OLEDB:Engine Type=4;"
rs.CursorLocation = adUseClient
rs.Open "SELECT * FROM TABLE_1", cnn, adOpenStatic, adLockReadOnly
rs.Filter = "Col2 = 8"
Set DataGrid1.DataSource = rs
Make sure that you do not close either the Recordset or the Connection.
Paul
~~~~
Microsoft MVP (Visual Basic)
.
- References:
- Re: Any reason why accessing Access should slowdown?
- From: Paul Clement
- Re: Any reason why accessing Access should slowdown?
- From: JohnBury
- Re: Any reason why accessing Access should slowdown?
- Prev by Date: Re: Any reason why accessing Access should slowdown?
- Next by Date: VB code to populate ComboBox based on two tables
- Previous by thread: Re: Any reason why accessing Access should slowdown?
- Next by thread: Re: Querying a database
- Index(es):
Relevant Pages
|
Loading