Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / May 2008

Tip: Looking for answers? Try searching our database.

Data typed appears slowly

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Derrick - 01 May 2008 00:51 GMT
I apologize if this is more appropriate for the forms group.

We recently upgraded to Office 2007, and now one of the Access databases has
a problem with being slow.  The file type is an MDE, and whenever a user
attempts to type data into a form (which represents a new record) it takes a
second or two for the data to appear on the screen.  The MDE was in 2003
format, but even after converting it to 2007 the problem still appears to be
there.

Any help would be appreciated
Arvin Meyer [MVP] - 01 May 2008 01:50 GMT
MDEs cannot be converted, so you must have had the original MDB files to
convert. Office 2007 uses significantly more resource than earlier versions
so I'd suggest a minimum of 1 GB of RAM on a fast machine. I find that even
2 GB is a bit slow running Access 2007 on Vista. My latest machine has 3 GB
of DDR3 RAM.

Try running your app on a fast machine to see if that may be your problem.
If that still doesn't help, there are a number of performance enhancements
discussed on Tony Toews web site:

Performance:
http://www.granite.ab.ca/access/performancefaq.htm
Signature

Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

>I apologize if this is more appropriate for the forms group.
>
[quoted text clipped - 9 lines]
>
> Any help would be appreciated
Derrick - 01 May 2008 16:03 GMT
Thanks for the info.  I was taking the user' word on the conversion of the
mde, so she must have had the mdb file as you said.
Only one of the people trying to access the file is using Vista, the others
are still on XP, though the XP users also do only have 1 GB of RAM so that
could very well still be the choke-point.  I'll try your suggestions and let
you know the results.
Thanks again

> MDEs cannot be converted, so you must have had the original MDB files to
> convert. Office 2007 uses significantly more resource than earlier versions
[quoted text clipped - 21 lines]
> >
> > Any help would be appreciated
Derrick - 01 May 2008 18:06 GMT
I have a little more info:
Apparently this was an Access 97 DB that was converted to 2003 format, and
now to 2007.  Also, other databases don't seem to have this issue, only this
one database has the slowdown.
I copied the database locally and I still have the issue, so I think that
should eliminate the network speed aspect.  I am using Vista and 2007, but I
also have a 3 GHz machine with 2 GB of RAM.
Thanks again in advance,
Derrick

> Thanks for the info.  I was taking the user' word on the conversion of the
> mde, so she must have had the mdb file as you said.
[quoted text clipped - 29 lines]
> > >
> > > Any help would be appreciated
Arvin Meyer [MVP] - 01 May 2008 21:50 GMT
Make a copy of the original MDB then try running the database in it's 2003
form, without converting it or making an MDE. See if the issue still occurs.
It is important to keep the original file. In fact you may want to make a
brand new, empty, 2003 database, and import all the objects into it, so that
it will be pristine. Try running it directly as an MDB, then convert it and
try running it as an MDE.

There may be other issues with Vista or Office 2007, but if other databases
are running OK, in all likelihood it is an issue with this one database.
Going over the points in the previously mentioned Performance FAQ will
hopefully help.
Signature

Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

>I have a little more info:
> Apparently this was an Access 97 DB that was converted to 2003 format, and
[quoted text clipped - 56 lines]
>> > >
>> > > Any help would be appreciated
Tony Toews [MVP] - 02 May 2008 01:25 GMT
>Apparently this was an Access 97 DB that was converted to 2003 format, and
>now to 2007.  Also, other databases don't seem to have this issue, only this
>one database has the slowdown.
>I copied the database locally and I still have the issue, so I think that
>should eliminate the network speed aspect.  I am using Vista and 2007, but I
>also have a 3 GHz machine with 2 GB of RAM.

There have been isolated reports of this problem with respect to A2007
but no real good resolution yet.

I'd suggest importing the MDB into a new MDB and see if that helps.

The Performance FAQ doesn't mention this problem yet.

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
  Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Derrick - 02 May 2008 23:52 GMT
I've gone through the FAQ but nothing there seems to apply to this situation
or the things that do don't lead to a fix.  I did also import the items into
a new MDB, but to no avail.  It seems a bit faster, but not by enough.  Could
the fact that it's being accessed across the network hurt the performance
enough?  I read one item (and it may have been in the FAQ, I can't remember
at this point) that says you should try putting the database at the root
level of the mapped drive.  It's not at the root level where we are running
it, but it is only one subfolder deep.
This database didn't give any problems in 97 and 2003, just in 2007.
Thanks again for the help.

> >Apparently this was an Access 97 DB that was converted to 2003 format, and
> >now to 2007.  Also, other databases don't seem to have this issue, only this
[quoted text clipped - 11 lines]
>
> Tony
Derrick - 05 May 2008 17:49 GMT
I made, what some could rightfully call, a stupid mistake when performing the
import.  I was importing the items into a 2003 DB then converting it to 2007
instead of going straight to a 2007 DB.  Once I did that, the speed issue
went away.
Thanks again for the help, and I'm sorry I missed that earlier.

> I've gone through the FAQ but nothing there seems to apply to this situation
> or the things that do don't lead to a fix.  I did also import the items into
[quoted text clipped - 22 lines]
> >
> > Tony
Tony Toews [MVP] - 14 May 2008 02:53 GMT
>I made, what some could rightfully call, a stupid mistake when performing the
>import.  I was importing the items into a 2003 DB then converting it to 2007
>instead of going straight to a 2007 DB.  Once I did that, the speed issue
>went away.

Ah, now that's interesting.  Thanks for posting back the solution.

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
  Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.