Form Design slowness in Access 2003

[Mike Nygard]

I'm experiencing extremely slow response times in design mode of my
forms since moving to Access 2003. Simply dragging a button to a
different position on the form takes 30 seconds or more. The record
source for my form is an ODBC passthrough query to an Oracle database.
I have two XP system identically configured except that one has
Access 2000 and the other with Access 2003. I only have this problem
with Access 2003. The Access 2003 system uses a default file format of
Access 2000.

Not sure what is causing the slowness. Any suggestions would be
appreciated. Thanks.

[Keith Wilby]

ny****@mr.net (Mike Nygard) wrote:

Not sure what is causing the slowness. Any suggestions would be
appreciated.

This is certainly worth a look:

<http://members.iinet.net.au/~allenbrowne/ser-48.html#usability>

Regards,
Keith.
www.keithwilby.com

[Mike Nygard]

Keith Wilby <ke*********@AwayWithYerCrap.com> wrote in message news:<Xn************************@10.15.188.42>...

ny****@mr.net (Mike Nygard) wrote:

Not sure what is causing the slowness. Any suggestions would be
appreciated.

This is certainly worth a look:

<http://members.iinet.net.au/~allenbrowne/ser-48.html#usability>

Regards,
Keith.
www.keithwilby.com

Thanks for you reply. That had a lot of good information in it but
none of it's suggestions seemed to help. When I remove the record
source from the form it seems to work just fine. It's almost like the
passthrough query in my data source is executing each time I make a
change to the form in design mode. Any other suggestions?

[Tony Toews]

ny****@mr.net (Mike Nygard) wrote:

Thanks for you reply. That had a lot of good information in it but
none of it's suggestions seemed to help. When I remove the record
source from the form it seems to work just fine. It's almost like the
passthrough query in my data source is executing each time I make a
change to the form in design mode. Any other suggestions?

That actually could make a lot of sense. I know that there's a significant
difference in performance when editing a form when the FE MDB is linked to BE MDB on
a server vs. locally.

Can you try opening up the passthrough query separately and leaving it open while you
work on the form?

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 Toews]

ny****@mr.net (Mike Nygard) wrote:

It's almost like the
passthrough query in my data source is executing each time I make a
change to the form in design mode. Any other suggestions?

Although when I reread your original posting it doesn't make any sense that there's a
difference between A2000 and A2003.

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

[Tim Marshall]

Mike Nygard wrote:

I'm experiencing extremely slow response times in design mode of my
forms since moving to Access 2003. Simply dragging a button to a
different position on the form takes 30 seconds or more. The record
source for my form is an ODBC passthrough query to an Oracle database.

I often had that problem with Access 97 when editing a form bound to a
pass through query. Most pronounced when the query returned a large
number of records and/or when the network was slowed down for whatever
reason.

Other than Oracle SQL tuning (joins coming AFTER criteria, etc), what
has helped me in the past is to take the pass through query and tack on
one or more criteria in the where clause that limit the results to only
a few records that represent what I'm trying to do. After the form was
perfected, I'd drop the special criteria.
--
Tim
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

[Mike Nygard]

Still no luck. Even though the passthrough query is slow, it is
tolerable in Access 2000 where it only happens once during form
startup. In Access 2000 I can open the form in design mode and it pops
up instantly. Opening the form in design mode In Access 2003
apparently causes the passthrough query to execute. All subsequent
changes in design mode (e.g. moving a button) cause the query to
execute as well. I'm not certain that it is a 2000 vs. 2003 issue.
It seems like there must be some configuration setting that can be
turned on or off to prevent this from happening. The ODBC
configuration is identical between the two machines. I'm using the
Oracle 8 ODBC driver. Anyone else had this problem?

[oraclevsmicrosoft]

I experiment these kind of trouble while migrating from 97 to 2003.
It appears that some security informations in linked table may cause
some troubles.
If you are using Ms Access security features, try to redefine your
linked tables, that was our solution.
Here you will find some vb code to do that without 150 clicks:

http://oraclevsmicrosoft.blogspot.co...able-views-in-
access.html

http://oraclevsmicrosoft.blogspot.com

Hope this help.
Thank you for your feed back.

OracleVsMicrosoft
ny****@mr.net (Mike Nygard) wrote in message news:<2b**************************@posting.google. com>...

Still no luck. Even though the passthrough query is slow, it is
tolerable in Access 2000 where it only happens once during form
startup. In Access 2000 I can open the form in design mode and it pops
up instantly. Opening the form in design mode In Access 2003
apparently causes the passthrough query to execute. All subsequent
changes in design mode (e.g. moving a button) cause the query to
execute as well. I'm not certain that it is a 2000 vs. 2003 issue.
It seems like there must be some configuration setting that can be
turned on or off to prevent this from happening. The ODBC
configuration is identical between the two machines. I'm using the
Oracle 8 ODBC driver. Anyone else had this problem?