My Assistant
![]() ![]() |
|
|
Jun 9 2010, 04:56 PM
Post
#1
|
|
|
UtterAccess Enthusiast Posts: 53 From: Alaska |
Hi All,
I have a tiny and super simple application running on an HP laptop for a local charity. This laptop's installation of Access has never been stable. See this thread. I have just encountered two problems, perhaps related to Access's installation. I've posted the two problems on different threads, in case they are not related. The other problem is here. This problem: I can't make any changes in an VBA module without Access shutting down. I get the following, not unfamiliar, message: Microsoft Access has encountered a problem and needs to close. Sorry etc. Send error report etc. Access shuts down, creates a backup copy and then fires up again. The error happens again after typing some 20 characters into a module. I have opened up a new database and imported the application into it, renamed it, and the same error occurs. I haven't yet decompiled it as my decompile notes are home. Any thoughts? Thanks, Russell PS My apologies, I see that I have posted this in the wrong forum and don't know how to move it. This post has been edited by rslheath: Jun 9 2010, 05:08 PM |
|
|
|
Jun 10 2010, 04:09 AM
Post
#2
|
|
|
UtterAccess VIP Posts: 5,508 From: Brixton, front line |
Hi there, do you have any timer events in any of your form's modules? This can cause issues of the form is open whilst you try and edit code, but not normally a crash.
I guess you have made sure all your code compiles. Compiling sounds like it would be a useful thing to do. A quick search of UA will show you how to.do it. One thing I have noticed to cause a crash recently is starting to write a function in the immediate window and then moving focus back to the editor or to another open program and leaving a syntactically incorrect/incomplete statement in the immediate window. CODE ?replace(txtTest, "bla If I leave a statement like that in the immediate window Access will sometimes crash. The only workaround is not to make sure you don't leave bad statements in the window. Otherwise, have you made sure you have all updates,service packs etc installed? Check on microsoftupdate.com Hth, d |
|
|
|
Jun 11 2010, 12:31 PM
Post
#3
|
|
|
UtterAccess Enthusiast Posts: 53 From: Alaska |
Thanks David,
The program compiles (there's only a few lines of code in the entire ap); there's nothing in the immediate window; no timer events; and I reinstalled Access and posted all the updates a couple of months ago when I first began having trouble with this installation. (The ap works flawlessly on my machine). I will check when I get back to their office--I believe I configured the machine to check for auto updates--that no new updates have come out since then. This installation of Access has been a tremendous mystery and frustration to me--and the irony is that the application itself took only a morning to throw together--there's nothing to it. Thanks again, Russell |
|
|
|
Jun 24 2010, 11:56 AM
Post
#4
|
|
|
Retired Moderator Posts: 8,589 From: Lansing, MI |
I've encountered this many times. Do you have any VBA add-ins like Mztools etc? I have that and a custom add-in. To prevent the crash run any form that has VBA or hold down shift when opening the VBE. If you hold down shift you'll have to start any add-ins yourself. I don't know what causes this I've just learned to deal with it. I don't think it's PC related.
|
|
|
|
![]() ![]() |
|
Go to Top · Lo-Fi Version | Time is now: 19th June 2013 - 08:40 PM |