Saving form changes hangs.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All,

I'm trying to figure out a problem I have. If I make a change to the
form module and click save, the windows just hangs. You can see the vba
module window switch
between [Form Name] and [running] [Form Name]

has anybody run into this?
 
You can probably solve this by getting rid of Name AutoCorrect, and
decompiling.

Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html
 
Thank you, this seems to have solved my problem.

-Michael


Allen Browne said:
You can probably solve this by getting rid of Name AutoCorrect, and
decompiling.

Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html


--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

michael said:
Hi All,

I'm trying to figure out a problem I have. If I make a change to the
form module and click save, the windows just hangs. You can see the vba
module window switch
between [Form Name] and [running] [Form Name]

has anybody run into this?
 
I forgot to mention, that if you copied the mdb to another machine we could
not reproduce this error. Is this meta data/index info stored in the ldb
file?

Thanks again
Michael

Allen Browne said:
You can probably solve this by getting rid of Name AutoCorrect, and
decompiling.

Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html


--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

michael said:
Hi All,

I'm trying to figure out a problem I have. If I make a change to the
form module and click save, the windows just hangs. You can see the vba
module window switch
between [Form Name] and [running] [Form Name]

has anybody run into this?
 
The ldb file contains locking information. It should be automatically
deleted once no users have the database open any longer. If not, you can
delete the file yourself.

If exactly the same database works on one machine and not on another, and
you have already re-installed Office, there has to be a difference in
version of either the Office service pack or the JET service pack. You can
determine the Office service pack in Acces under Help About, e.g. "Access
2002 SP3". To determine the JET service pack, locate the file msjet40.dll
(typically in windows\system32), right-click and choose Properties. The
Version tab should show 4.0.8xxx.0, where the xxx do not matter, but if you
don't see the 8, get SP8 for JET 4.

The service packs are at:
http://support.microsoft.com/gp/sp

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

michael said:
I forgot to mention, that if you copied the mdb to another machine we could
not reproduce this error. Is this meta data/index info stored in the ldb
file?

Thanks again
Michael

Allen Browne said:
You can probably solve this by getting rid of Name AutoCorrect, and
decompiling.

Try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database
by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect
errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html


michael said:
Hi All,

I'm trying to figure out a problem I have. If I make a change to the
form module and click save, the windows just hangs. You can see the
vba
module window switch
between [Form Name] and [running] [Form Name]

has anybody run into this?
 
Back
Top