I compact it daily. Yes the database is split.
This did, in fact, turn out to be the result of 1 person having the db open. I found out who it was, had them close it and everything went back to normal.
I don't understand why ONE person having the file open (through a front end interface) would slow things down SO MUCH. Is there a lock issue here?
Thanks
-Lee
--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Lee
>
> When was the last time you compacted the back end? You did split the database, right?
>
> Regards,
> Bill Mosca, Founder - MS_Access_Professionals
> http://www.thatlldoit.com
> Microsoft Office Access MVP
> https://mvp.support.microsoft.com/profile/Bill.Mosca
>
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "Lee" <leevt99@> wrote:
> >
> > Nope, i haven't changed a thing. I'm sure network latency is part of it, especially since the database files are buried deep in folders (no choice here, it's how the network is set up), but to go from 5-10 minutes to over an hour seems strange. I'm guessing it's either some unaccounted for scenario with data (less likely) or some sort of concurrency issue.
> >
> > The app is designed so that a main form is opened and menu items switch the subform around to whatever form the users want to work on. Could that be part of the slowness? Although all of my programs use the same system/setup and only this one is as slow as it is.
> >
> > Thanks
> > -Lee
> >
> > --- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@> wrote:
> > >
> > > Lee-
> > >
> > > Did you change anything about the way the app runs? Perhaps before users were
> > > leaving a form open as they navigated to other forms. It could also be an issue
> > > with your network.
> > >
> > > 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/
> > > (Paris, France)
> > >
> > > ---------------------------------------
> > >
> > > From: MS_Access_Professionals@yahoogroups.com
> > > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Lee
> > > Sent: Monday, March 26, 2012 10:47 PM
> > > To: MS_Access_Professionals@yahoogroups.com
> > > Subject: 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]
> > > >
> > >
> >
>
Tidak ada komentar:
Posting Komentar