Performance Slowdown with Access 207

[Tigerfish]

I recently converted an application from Access 2000 to Access 2007. It's a
large, complex application that has performed well for several years. Front
ends run on both Windows XP and Vista. The back end is on a Linux server.
Since the conversion performance has slowed dramatically. A form that used
to open in 3 seconds now takes 30 seconds. Performance is OK when the back
end is copied to the local drive. It's equally slow when tested with the
back end on the Linux serve and a Buffalo stand-alone drive. User are
frustrated with the sluggish performance, and the main decision maker doesn't
want to re-write the app to simplify the main forms.

Is this performace slow down typical of Access 2007? Any suggestion on how
speed things up?

 

[Robert Morley]

Have you tried installing all the various hotfixes and/or service packs? I
have no experience with it myself, but I know the original A2007 had
problems with ADP files being exceptionally slow; perhaps something similar
is occurring here.



Rob

 

[Tigerfish]

I have installed service pack 1. I haven't installed hotfixes as I don't see
any that seem to address this particular problem. As some of the hot fixes
specifically state that they should only be installed for a very specific fix
I don't automatically install them. Do you know of any that might help?

 

[Robert Morley]

Not unless you're using an ADP, and I believe SP1 addressed that problem
anyway. Sorry.


Rob

 

[mochatrpl]

I have installed service pack 1.  I haven't installed hotfixes as I don't see
any that seem to address this particular problem.  As some of the hot fixes
specifically state that they should only be installed for a very specific fix
I don't automatically install them.  Do you know of any that might help?
--
Michelle





- Show quoted text -

I have also experienced the very same slowdown. My database uses a
complex form that used open very quickly in 2000 but is now
extremly... painfully slow to open. I am even re-writing the database
to eliminate the bells and whistles that originally made this a
sucess. I also would like to hear from anyone else that has figured
out how to get around this.

- Randy

 

[Rick A.B.]

I recently converted an application from Access 2000 to Access 2007.  It's a
large, complex application that has performed well for several years.  Front
ends run on both Windows XP and Vista.  The back end is on a Linux server.  
Since the conversion performance has slowed dramatically.  A form that used
to open in 3 seconds now takes 30 seconds.  Performance is OK when the back
end is copied to the local drive.  It's equally slow when tested with the
back end on the Linux serve and a Buffalo stand-alone drive.  User are
frustrated with the sluggish performance, and the main decision maker doesn't
want to re-write the app to simplify the main forms.  

Is this performace slow down typical of Access 2007?  Any suggestion on how
speed things up?  

Michelle & Randy

Check out Tony Toew's Microsoft Access Performance FAQ at
http://www.granite.ab.ca/access/performancefaq.htm

I've converted a number of databases to 2007 and have had very few
problems. I would suspect that you'd find something in Tony's list
that would help you.

Hope that helps.

Rick

 

[Albert D. Kallal]

Have you tried using a persistent connection ?

 

[Jim Burke in Novi]

When you converted the appl did it grow significantly in size? You may need
to compact, decompile and re-compact the converted version. Just a thought. I
had a large appl that had 'bloated' over time (not related to new version)
and it ran fine locally but very slowly on a network. I was compacting but
not decompiling, and over time it got huge. Doing a compact, Decompile and
another compact shrunk it way down and got rid of the performance problem. I
now do this on a regular basis. Maybe converting the appl 'bloats' it?

 

[Tigerfish]

Thanks for the input. I've decompiled and compacted. I've made decompiling
standard practice when I install updates. It made no difference.

 

[Tigerfish]

There's a dummy form open at all times.

 

[Tigerfish]

Thanks. I'm glad this problem is not normal with Access 2007. I'm going
through Tony's list. So far I'm having trouble getting the network support
folks on boad.

 

[Tigerfish]

Rick,

Perhaps I should start a new thread for this, but since you mentioned that
you've converted a number of apps to 2007 perhaps you know the answer.

I've tried using the code in Tony Toew's FAQ to load the recordsource and
rowsource for form controls when the form loads. I've spent all day trying
to make the code work. The code to set rowsource for combo boxes and list
boxes works. But I can't set the record source for subforms. I've searched
online for information abaout the specific error I'm getting and have found
many replies, and I've tried the format suggested. Yet I keep getting the
same error and I'm wondering if this something that has changed with 2007
that I'm not aware of.

When I try to set the record source for a sub form using the following code:

ctl.Form.RecordSource = ctl.Form.Tag

I get an error message 2455 - "You've entered an expression that has an
invalid reference to the property Form/Report."

I've tried explicitly setting the record source by stipulating the full name
of the form and subform and still I get the same error message. I've
followed threads where other users have asked this questions and responded
that this code works. But I've tried this for some hours now, determined to
make it work, and it doesn't.

Do you know if it is possible to set a subform's record source using
control.form.recordsource in Access 2007? I'm stumped.

 

[Rick A.B.]

Rick,

Perhaps I should start a new thread for this, but since you mentioned that
you've converted a number of apps to 2007 perhaps you know the answer.

I've tried using the code in Tony Toew's FAQ to load the recordsource and
rowsource for form controls when the form loads.  I've spent all day trying
to make the code work.  The code to set rowsource for combo boxes and list
boxes works.  But I can't set the record source for subforms.  I've searched
online for information abaout the specific error I'm getting and have found
many replies, and I've tried the format suggested.  Yet I keep getting the
same error and I'm wondering if this something that has changed with 2007
that I'm not aware of.  

When I try to set the record source for a sub form using the following code:

ctl.Form.RecordSource = ctl.Form.Tag

I get an error message 2455 - "You've entered an expression that has an
invalid reference to the property Form/Report."  

I've tried explicitly setting the record source by stipulating the full name
of the form and subform and still I get the same error message.  I've
followed threads where other users have asked this questions and responded
that this code works.  But I've tried this for some hours now, determined to
make it work, and it doesn't.

Do you know if it is possible to set a subform's record source using
control.form.recordsource in Access 2007?  I'm stumped.

Michelle,

I'm not familar with Tony's code, maybe he will stop by here and
help. What is the exact code your trying to use to set the subforms
recordsource? Could you post it? I take it this is an unbound form
or subform so you can't use the Link Child Fields and Link Master
Fields properties. What event are you using to set the Subforms
recordsource from? Give us a little more information.

Rick