From: Pat2000 on
My client's database is set up with a split database, using frontend and
backend .mdb files. I did not set it up and I'm still trying to familiarize
myself with the it. I've had Access 2007 training, but I'm still basically a
newbie.

Client's description of problem:
"Generally we only have one person inputting data to the database at any
given time, however we are noticing that the program seems to be getting
slower at accepting data. What happens is during transaction entering, a
little note at the bottom of the screen says "Calculating" and we are not
able to move to the next field until that is completed. The girls are
telling me this is becoming more frequent and stalling entry for longer
periods of time."

Any suggestion for where I could begin looking would be greatly appreciated.
Thanks in advance!



From: Daniel Pineault on
First, make a back-up of everything (just in case)
Then perform a compact and repair. See if that helps at all.

Out of curiousity, how many records does your db currently house?
Is the front-end on the user's pc and the back-end on a central server?
What type of network is it deployed on? LAN 10/100?
How many sub-directories deep is the database saved in?

There can be numerous reason for the slow down. In one instance, it had
nothing to do with the db, but rather the network. The network was simply
overwhelmed by all the user traffic (unrelated to the database) so it was
slow to respond to db actions. Eventually the client switch the fiberoptics
and, poof, the problem was gone!

When you get this message, moving from one control to another, is there code
behind the control? What is it?
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"Pat2000" wrote:

> My client's database is set up with a split database, using frontend and
> backend .mdb files. I did not set it up and I'm still trying to familiarize
> myself with the it. I've had Access 2007 training, but I'm still basically a
> newbie.
>
> Client's description of problem:
> "Generally we only have one person inputting data to the database at any
> given time, however we are noticing that the program seems to be getting
> slower at accepting data. What happens is during transaction entering, a
> little note at the bottom of the screen says "Calculating" and we are not
> able to move to the next field until that is completed. The girls are
> telling me this is becoming more frequent and stalling entry for longer
> periods of time."
>
> Any suggestion for where I could begin looking would be greatly appreciated.
> Thanks in advance!
>
>
>
From: Pat2000 on
Daniel,
Thank you for responding. I haven't tried the compact and repair yet, but
thought I'd try to answer some of your questions first.

I'm not sure how many records there are, but the backend contains 20 tables
and the file size is 99.5MB. The backend is on a central server and the
frontend is on each of 5 users PCs. I'm not sure about the LAN 10/100. but
the database is 6 sub-directories deep.

I'm away from the office and haven't logged in to personally see the
slowdown or error messages. I'm just going on what the office manager
reported to me in an email.

Thanks.

"Daniel Pineault" wrote:

> First, make a back-up of everything (just in case)
> Then perform a compact and repair. See if that helps at all.
>
> Out of curiousity, how many records does your db currently house?
> Is the front-end on the user's pc and the back-end on a central server?
> What type of network is it deployed on? LAN 10/100?
> How many sub-directories deep is the database saved in?
>
> There can be numerous reason for the slow down. In one instance, it had
> nothing to do with the db, but rather the network. The network was simply
> overwhelmed by all the user traffic (unrelated to the database) so it was
> slow to respond to db actions. Eventually the client switch the fiberoptics
> and, poof, the problem was gone!
>
> When you get this message, moving from one control to another, is there code
> behind the control? What is it?
> --
> Hope this helps,
>
> Daniel Pineault
> http://www.cardaconsultants.com/
> For Access Tips and Examples: http://www.devhut.net
> Please rate this post using the vote buttons if it was helpful.
>
>
>
> "Pat2000" wrote:
>
> > My client's database is set up with a split database, using frontend and
> > backend .mdb files. I did not set it up and I'm still trying to familiarize
> > myself with the it. I've had Access 2007 training, but I'm still basically a
> > newbie.
> >
> > Client's description of problem:
> > "Generally we only have one person inputting data to the database at any
> > given time, however we are noticing that the program seems to be getting
> > slower at accepting data. What happens is during transaction entering, a
> > little note at the bottom of the screen says "Calculating" and we are not
> > able to move to the next field until that is completed. The girls are
> > telling me this is becoming more frequent and stalling entry for longer
> > periods of time."
> >
> > Any suggestion for where I could begin looking would be greatly appreciated.
> > Thanks in advance!
> >
> >
> >
From: Daniel Pineault on
I would start with a compact. Do they ever do a compact & repair?
I would also try and place the database in a 1st or 2nd level directory.

See what that does and post back.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"Pat2000" wrote:

> Daniel,
> Thank you for responding. I haven't tried the compact and repair yet, but
> thought I'd try to answer some of your questions first.
>
> I'm not sure how many records there are, but the backend contains 20 tables
> and the file size is 99.5MB. The backend is on a central server and the
> frontend is on each of 5 users PCs. I'm not sure about the LAN 10/100. but
> the database is 6 sub-directories deep.
>
> I'm away from the office and haven't logged in to personally see the
> slowdown or error messages. I'm just going on what the office manager
> reported to me in an email.
>
> Thanks.
>
> "Daniel Pineault" wrote:
>
> > First, make a back-up of everything (just in case)
> > Then perform a compact and repair. See if that helps at all.
> >
> > Out of curiousity, how many records does your db currently house?
> > Is the front-end on the user's pc and the back-end on a central server?
> > What type of network is it deployed on? LAN 10/100?
> > How many sub-directories deep is the database saved in?
> >
> > There can be numerous reason for the slow down. In one instance, it had
> > nothing to do with the db, but rather the network. The network was simply
> > overwhelmed by all the user traffic (unrelated to the database) so it was
> > slow to respond to db actions. Eventually the client switch the fiberoptics
> > and, poof, the problem was gone!
> >
> > When you get this message, moving from one control to another, is there code
> > behind the control? What is it?
> > --
> > Hope this helps,
> >
> > Daniel Pineault
> > http://www.cardaconsultants.com/
> > For Access Tips and Examples: http://www.devhut.net
> > Please rate this post using the vote buttons if it was helpful.
> >
> >
> >
> > "Pat2000" wrote:
> >
> > > My client's database is set up with a split database, using frontend and
> > > backend .mdb files. I did not set it up and I'm still trying to familiarize
> > > myself with the it. I've had Access 2007 training, but I'm still basically a
> > > newbie.
> > >
> > > Client's description of problem:
> > > "Generally we only have one person inputting data to the database at any
> > > given time, however we are noticing that the program seems to be getting
> > > slower at accepting data. What happens is during transaction entering, a
> > > little note at the bottom of the screen says "Calculating" and we are not
> > > able to move to the next field until that is completed. The girls are
> > > telling me this is becoming more frequent and stalling entry for longer
> > > periods of time."
> > >
> > > Any suggestion for where I could begin looking would be greatly appreciated.
> > > Thanks in advance!
> > >
> > >
> > >