ACCESS FEED: Re: [MS_AccessPros] Database performance with more than 1 concurrent user

Senin, 26 Maret 2012

Re: [MS_AccessPros] Database performance with more than 1 concurrent user

Thanks, I'll give this a try.

What I don't understand is why this came out of the blue. I haven't made any changes, but now everything runs dirt slow for everyone. The ONLY thing I can think of is some of the data changed to something that hasn't been accounted for, or there are some deadlock issues or something :/

Thanks
-Lee

--- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@...> wrote:
>
> Lee-
>
>
>
> One way to speed things up is to open any of the linked tables in the code in
> your startup form and leave the recordset open until the app ends. When you do
> this, Access builds the link to the server once and reuses it for all other
> tables.
>
>
>
> John Viescas, author
>
> Microsoft Office Access 2010 Inside Out
>
> Microsoft Office Access 2007 Inside Out
>
> Building Microsoft Access Applications
>
> Microsoft Office Access 2003 Inside Out
>
> SQL Queries for Mere Mortals
>
> <http://www.viescas.com/> http://www.viescas.com/
>
> (Paris, France)
>
>
>
>
>
>
>
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Lee
> Sent: Monday, March 26, 2012 8:05 PM
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] Database performance with more than 1 concurrent user
>
>
>
>
>
> Hi,
> I have a database used by about 6 people, usually there are only 2-3 in it at a
> time, but for some reason if there is more than one person in it, certain tasks
> go from about 30-40 seconds, to 10-15 minutes. Or from 50 minutes to 90 minutes.
>
> Could this be a record lock setting somewhere? I don't understand why there is
> such a speed discrepancy, particularly when the tasks being run are not writing
> to shared tables.
>
> Thanks
> -Lee
>
>
>
>
>
> [Non-text portions of this message have been removed]
>