Re: Problem with VBA created subform in Access 2007
- From: "Dirk Goldgar" <dg@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 22 Mar 2007 12:34:28 -0400
In news:D2CC94D3-DC93-4D21-8AE7-EB176BED2942@xxxxxxxxxxxxx,
Robert A. <RobertA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Dirk Thanks for the info, it is very insightful, but I am going to
need to throw another wrench in the gears. I need to explain I am not
the person who origially wrote the code, and I am coming into his a
little green so bare with me. I tried running the database on another
near identical computer and it runs fine. I tried a third and I get
the same problem. As it stands I have tried it on 5 computers and of
those, 1 runs it fine no delays to speak of.
I believe you are right about the code not being in a compiled state
at run time, which may cause the problem, But then why whould one
machine not be seeing the delay in the DB. Can you think of any
reason that a DB would see problem from one machine to the next?
Hmm. If those computers are all running the same version of Access, or
even if they are all running some version from Access 2000 to 2007, and
they all have about the same processing power (so it's not that the one
computer is extraordinarily fast), then I can only think of a couple of
factors that might be varying from computer to computer:
1. Name AutoCorrect. I mentioned this at the end of my last message:
One unrelated thing I can think of that *may* also be playing a part
in your delay is Name AutoCorrect. If you haven't turned that off,
I'd recommend doing so.
Did you check that out? I'm not sure if this is a setting that travels
with the .mdb file, or if it's an application-wide setting. If the
latter, it could be different on different computers.
2. User-authorization for exclusive database access.
This is really reaching, but in order to make a run-time design change
in your database, the user's file access has to be promoted from its
original shared access (assuming you've got the default options set) to
exclusive access. It could be that there's something about the
resolution of the necessary permissions that is just taking a lot longer
on most computers, but not on that one. Maybe that computer has its
default open mode set to exclusive access, or something.
--
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
.
- Follow-Ups:
- Re: Problem with VBA created subform in Access 2007
- From: Robert A.
- Re: Problem with VBA created subform in Access 2007
- References:
- Re: Problem with VBA created subform in Access 2007
- From: Dirk Goldgar
- Re: Problem with VBA created subform in Access 2007
- From: Dirk Goldgar
- Re: Problem with VBA created subform in Access 2007
- Prev by Date: Re: help with syntax
- Next by Date: RE: run module problem
- Previous by thread: Re: Problem with VBA created subform in Access 2007
- Next by thread: Re: Problem with VBA created subform in Access 2007
- Index(es):
Relevant Pages
|
