Database Performance

Shepenwepet

New member
Local time
Today, 09:32
Joined
Aug 28, 2006
Messages
6
I'd like to know whether other users have had performance problems with different versions of Access in a single environment.

In my office, two users are on A2007, and the rest of us are on A2003 or earlier. After some nasty conflicts in the (un-split) database when A2007 and A2003 users were in the same file, I split the database. Now the A2007 and A2003 people have individual frontends. Other than having a garbled LDB file, I haven't had any other conflicts between the two programs.

However, I have had some massively irritating problems ever since I split the database.

1)The Design View on my Front End runs very, very slow (like, five beats after every action to process).
2) If I try to edit one particular, very simple form, it will not return to form view... it is stuck in Design view. (That sounds like the form has been corrupted.)
3) The auto-save doesn't seem to be working... Access (2003) crashed on me yesterday and I lost an hour's work on a new form.

I've tried some of the database construction suggestions to speed performance in other posts - forms based on queries, record locking, short paths, etc., and have seen some improvement in overall performance, but none of these should affect design view. USING the database tends to be speedy-quick.

So, did our dalliance with A2007 mess up my database? Does any one else have experience with this? Or are these symptoms common with a slow network connection (the back end is on a server, front ends are on individual desktops)?

Thanks!
 
I also have terrible slowness problems in design view since once opening my front end in A2007. The slowness is othing to do with having a FE/BE but I do think that A2007 has screwed something.

The FE runs OK as an MDE file but trying to get objects into design view is painful!!
 
This is a shot in the dark. By any chance do any of the forms in this DB have a timer running in the background on a hidden startup form?

Timers active on forms are known to cause issues.
 
I have issues with some of my larger DB's when editing the FE. It's slow like that but if you unlink the form while editing it helps...at least here.

I have a timer running in some of these DB's, but it should be bypassed when I startup with shift key so that shouldn't affect mine.
 
DocMan, I didn't create a timer in any of my code so I don't think that's the case. I have a form designated at startup... a basic switchboard and the only code on that is wizard-created command buttons and a few subform requeries.

odin1701, I tried removing the RecordSource to my forms before making structural changes as a test. It was faster for a bit but with subsequent switches between Form View and Design View it slowed down again, then refused to switch to Form View at all. I'm not sure communication with the back end is the issue.
 

Users who are viewing this thread

Back
Top Bottom