Access 2007: Design Mode pauses when selecting subform

[joebb3]

I've have searched for several days to find an answer to this and I have tried many dubious "fixes" with no joy.

Background:
My database was designed in Access 2003. It is a Front End/Back End setup. The back end resides on a shared network resourse. I have not updated to 2007 File Format because there are still 2003 users accessing the db.

All of the typical 2003 speed tweaks are applied, AutoName Correct is off on the Front and Back End.

Problem:
In Form Design View, if the form has a subform, switching between the two can take 15-30 seconds for Access to resume operation.

If the main form has the focus and you click INTO the sub form, the pause happens. Then if you click OUT of the sub form, the pause happens again! Its drivin' me nuts! I can open the subform in design mode independantly and edit it, but that is a major pain and I shouldn't have to. Don't cha love "Upgrades".

Does anyone have any definative insight as to why this happens?

One of the fixes I've read: "Unlink all data when developing the forms." (Yeah... Right.)

Thanx!
Joe

 

[boblarson]

My suggestion? Make a copy of the backend to house on your computer and link your development copy to that while you are developing. Then, when ready to deploy or for live testing, relink to the backend on the server.

Local copies tend to not have these issues due to the network traffic issues.

Bob Larson
Free Access Tutorials and Samples:

http://www.btabdevelopment.com

 

[MajP]

What happens if you keep a persistent connection to the backend? Does it make a difference if another form is loaded?

 

[joebb3]

Bob,

Its a sizable database with links to several data sources... Could I write a script to autolink back and forth from Production to Active? Sure I could, but dang it... I shouldn't have to!

MajP,
Sadly, I have a persistent connetcion to the main data source via a hidden form. (That was one of the suggestins I had searched out with no joy.)

I have a sinking feeling that the reason it happens is that even in Design Mode, access tries to treat the form as if it was live, accessing the back ends needlessly. Unfortunately, I live and breath backends on shared resources over mediocre network connections.

Forgive me if I go on a rant here, but should 2k3 to 2k7 be an UPGRADE? There are some pretty basic things that were destroyed in 2K7...

- Hover on the Code Screen raely ever shws the value of what you are hovering over... Brilliant
- Ribbons... Need I say more?
- This stoopid persistent data accessing in design mode
- and many more.

All this BS so that I can use JPGs on my forms instead of Bitmaps. Yey.

Thanks,
Joe

PS... If anyone has a different suggestion, I'm willing to listen!

 

[boblarson]

Joe:

It isn't Access 2007 that is at fault here. It works just fine for me in my environment. So, I've got to surmise that it has to do with either your network or your file shares and how the data gets synched on the servers.



Bob Larson
Free Access Tutorials and Samples:

http://www.btabdevelopment.com

 

[joebb3]

Bob, Thanks for the comment. I realize that the network is the cause of the issues, my gripe is that, even in Design Mode, ACC2007 treats the form as if it were live accessing queries and control data needlessly.

I believe that MS "Knows" this and that was the reason for the new "feature", Layout View. A lot of good THAT does when there is coding involved.

There IS a question here...

Is it possible to sever this persistent connetion in design view WITHOUT relinking all of your data sources to a local drive during development?

 

[boblarson]

Nope, there isn't.

Bob Larson
FORMER Microsoft Access MVP (2008-2009, 2009-2010)
Free Tutorials/Samples/Tools:

http://www.btabdevelopment.com