Re: Problem with VBA created subform in Access 2007

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Dirk,
First I just want to thank you so much for helping me out, It's much
appreciated. Next time your in Chicago I'll take you out for a steak or
something.

Ok, on to the good stuff,

As far as Name autocorrect, in 2007 I can only assume that it is the
autocorrect options. There is no autocorrect option for Name. On one machine
that is showing the delay problem i turned all of the autocorrect options to
off, but I still see the delay. So I am not quite sure if i'm missing
something or I am not in the right place to get to these settings. Maybe you
could point me in the right direction.

On your permissions suggestion it got me thinking. Since the DB's are stored
on the local machine ( the DB is copied to local when there are any changes
made in the database stored on our server) I tried to connect two machines to
the DB on the network. I got a very interesting result. I got an error I have
not seen since Access 2000 " The database has been placed in a state by user
'Admin' on machine 'xxxxxxxxx' that prevents it from being opened or locked "
If memory serves me correct, this was an error in AC2000 that was fixed with
a service pack. The DB is shared and set that way, unless again, I am missing
something. You got any ideas on this one.

"Dirk Goldgar" wrote:

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)



.

Relevant Pages

  • Re: Problem with VBA created subform in Access 2007
    ... machine not be seeing the delay in the DB. ... User-authorization for exclusive database access. ... default open mode set to exclusive access, ...
    (microsoft.public.access.modulesdaovba)
  • Re: Prompting large number of records
    ... Where is the database? ... How are you displaying them? ... Is the delay in updating the display... ... and load in more as the user scrolls down. ...
    (microsoft.public.vb.general.discussion)
  • Re: bug in form event code
    ... database and immediately turn OFF the Name Autocorrect options, ... then open any VBA module and compile the code, ... don't import the problem form into a new db. ...
    (microsoft.public.access.formscoding)
  • Re: Urgent: Storage Card Mount and UnMount Event WM 5.0
    ... For the answer see the RequestDeviceNotifications API. ... Chris Tacke - Embedded MVP ... to the database when application loads and disconnect it on exit. ... triggered only after a delay, after analysis I beleive the delay is ...
    (microsoft.public.pocketpc.developer)
  • Re: Running Split Access2000 db on Network
    ... I turned off Name AutoCorrect options, and it really sped things up. ... >> This is a normal procedure, but when I run the database now it ... >> unsplit version of the database, but it makes it difficult to install ... There are only 5 clients. ...
    (comp.databases.ms-access)