Re: Access performace help


Thanks for the info..

The late biniding also did the trick ... from 12-15 seconds to open the form
to 2 to 3-4 seconds now. I still need to furhter fine tune this with the
ideas on your link..

Thanks


"Douglas J. Steele" wrote:

First thing to do is check the Access Performance FAQ Tony Toews has at
http://www.granite.ab.ca/access/performancefaq.htm

Answering your specific questions:
- Removing linked tables and replacing it with VBA code is unlikely to solve
the problem.
- For a Jet backend (i.e.: an MDB file), DAO is almost always better
- You can create an ADO recordset and set the form's Recordset property to
that recordset. See
http://msdn2.microsoft.com/en-us/library/aa173231(office.11).aspx for an
example. (I believe this capability was added in Access 2000)

Tony's FAQ should answer the rest of the questions.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Mohan" <Mohan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0FDA9D57-ED32-4238-A427-86EF50F738D0@xxxxxxxxxxxxxxxx
Hi
I develped a simple Access application to track projects. Application has
a
fron-end file (with forms, queries, modules) and a back-end file with data
only. All tables are linked tables from the front-end file.

The application works fine when both files are on the local drive. But
when
I move the data file to the network folder, the application is very slow
(about 10 - 15 seconds to open each screen).

I need suggestions for increasing performance
- Should I remove the linked tables and use DAO / ADO?
Which one is better DAO or ADO ?
If using ADO, how do I assign the record set created with ADO to the
form?
(I don't want to fill each filed thru code)
(Note: I have done ADO programming before in VB / I need to know how to
assign the forms record set to the records set created with the ADO code
(instead of the linked) if this is possible
- Is there any thing esle I should try (whitout removing the linked
tables) ?
- I did some research and set the subdata*** name property to none (if
its auto)




.

Quantcast