Performance issue

[Orna]

I upgraded a database from version 2003 to 2007 and I have a serious
performance problem.
One of the forms in the application contains 9 tabs and a lot of fields, the
problem is that this specific form is very very slow, but when I run it in
the 2003 version it is significantly faster.
I noticed the same problem in another application I upgraded.
Is that a known problem in access 2007?, is there a way to overcome it?

Thanks in advance,
Orna.

[ban...@gmail.com]

Hi,

Are there backend/frontend or one database?

First advice which improves performance is to remove subdatasheet view
(that is plus sign in related tables where you can see on table level
which records are related to parent table). For more details see
http://office.microsoft.com/en-us/access/HA102565411033.aspx.

Regards,
Branislav Mihaljev
Microsoft Access MVP

[Orna]

Hi,
1. Yes, there is a frontend and backend database.
2. I changed the property of subdatasheet to all tables to "None", this
didn't help much.
My assumption is that access 2007 can not deal with forms with a large
number of controls, because I had the same problem in another application I
upgraded. Is it possible?

Thanks,
Orna.

[ban...@gmail.com]

Hi,

There are lots of advices how to speed up forms loading i.e. are there
proper relationships, have you compacted database, does disk
defragmenting helps, are there enough RAM, have you used indexes, etc.

Does each subform loads slow? You can try to load subform by subform
only when it is needed. Without database to analyze I could not tell
much more.

Also you can try to move backend from "server" side to local computer,
relink the frontend and then try to load the form. Does it still takes
too much time to load?

[Orna]

Hi,

I finally solved the problem, I did several actions:
1. Compiled the VBA code.
2. Compacted the database
3. I changed some of the forms' code (for example instead of closing the
form each time the user exits, I changed the property "Visible" to false and
this way when the form opens again it doesn't load the controls again.
4. I ran the application with "runtime" command bar option.
5. And finally, what made the real change was surprisingly the "document
windows option", I changed it to "Tabbed Document" and the application is
running even faster than it was running in access 97.

Thanks again,

[muser]

Ο "Orna" <Or...@discussions.microsoft.com> έγραψε στο μήνυμα
news:F3ABCF03-009C-48E2...@microsoft.com...

>.hello ho are you

[Tony Toews [MVP]]

Orna <Or...@discussions.microsoft.com> wrote:

>3. I changed some of the forms' code (for example instead of closing the
>form each time the user exits, I changed the property "Visible" to false and
>this way when the form opens again it doesn't load the controls again.

On a complex form that would certainly help.

>5. And finally, what made the real change was surprisingly the "document
>windows option", I changed it to "Tabbed Document" and the application is
>running even faster than it was running in access 97.

Now that's very interesting. Thanks for posting.

Tony
--
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/

[Tony Toews [MVP]]

Orna <Or...@discussions.microsoft.com> wrote:

>5. And finally, what made the real change was surprisingly the "document
>windows option", I changed it to "Tabbed Document" and the application is
>running even faster than it was running in access 97.

Darn I should've looked at my website. There's a hotfix for that.
See the first section at the Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

[a a r o n . k e m p f @ g m a i l . c o m]

----------------------------------------------------------------------------------------
Access, however, is not perfect. Performance degrades significantly as
the database size increases. The database is also prone to corruption.
Finally, starting with an Access database has tempted many developers
to do a dangerous thing. Sometimes a single-user application becomes
popular enough that there's a desire for it to be used by multiple
simultaneous users. The temptation is to just move the Access database
file to a network share, copy the application to multiple machines,
and let many users connect simultaneously. Access performance drops
off quickly with multiple users, and it's highly unlikely that an
application that was designed for a single user will work reliably
with concurrent users.

Http://msdn.microsoft.com/en-us/library/aa730870(VS.80).aspx
----------------------------------------------------------------------------------------

> > > > First advice which improvesperformanceis to remove subdatasheet view

> > > > (that is plus sign in related tables where you can see on table level
> > > > which records are related to parent table). For more details see
> > > >http://office.microsoft.com/en-us/access/HA102565411033.aspx.
>
> > > > Regards,
> > > > Branislav Mihaljev
> > > >Microsoft AccessMVP
>
> > Hi,
>
> > There are lots of advices how to speed up forms loading i.e. are there
> > proper relationships, have you compacted database, does disk
> > defragmenting helps, are there enough RAM, have you used indexes, etc.
>
> > Does each subform loads slow? You can try to load subform by subform
> > only when it is needed. Without database to analyze I could not tell
> > much more.
>
> > Also you can try to move backend from "server" side to local computer,
> > relink the frontend and then try to load the form. Does it still takes
> > too much time to load?
>
> > Regards,
> > Branislav Mihaljev

> >Microsoft AccessMVP- Hide quoted text -
>
> - Show quoted text -

[Tony Toews [MVP]]

"a a r o n . k e m p f @ g m a i l . c o m" <aaron...@gmail.com>
wrote:

>Access, however, is not perfect.

And that paragraph is exceedingly slanted and by someone who clearly
doesn't understand Access.

How many hours did it take you to find that paragraph?

>On Dec 4, 12:03 am, Orna <O...@discussions.microsoft.com> wrote:

And you replied to a question that was about 22 days ago. I'm sure
it's quite relevant.

[Orna]

Hi Tony,

I noticed in the last few days that there is significant difference in
performance when I work with different screen resolutions, the application
works much faster with higher resolution.
Is there any explanation to this behaviour?

Thanks in advance,
Orna.

[John W. Vinson]

On Tue, 6 Jan 2009 23:46:00 -0800, Orna <Or...@discussions.microsoft.com>
wrote:

>Hi Tony,
>
>I noticed in the last few days that there is significant difference in
>performance when I work with different screen resolutions, the application
>works much faster with higher resolution.
>Is there any explanation to this behaviour?

I wonder if there's a problem with your computer's video driver, or with its
interaction with Windows or Access? I don't think this is specifically an
Access problem, since the program has to use the driver to do anything on the
screen.
--

John W. Vinson [MVP]

[Tony Toews [MVP]]

Orna <Or...@discussions.microsoft.com> wrote:

>I noticed in the last few days that there is significant difference in
>performance when I work with different screen resolutions, the application
>works much faster with higher resolution.
>Is there any explanation to this behaviour?

Yowzer. I have no explanation for this at all. That doesn't make any
sense.

[David W. Fenton]

=?Utf-8?B?T3JuYQ==?= <Or...@discussions.microsoft.com> wrote in
news:A3C01758-EF3E-445A...@microsoft.com:

> I noticed in the last few days that there is significant
> difference in performance when I work with different screen
> resolutions, the application works much faster with higher
> resolution. Is there any explanation to this behaviour?

Do other applications exhibit any performance differences with the
different resolutions?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/