Startup Form Keeps Failing to Startup

[Jay Chan]

The startup form of my MS-Access program (MDB) keeps failing to
startup. I have done the usual thing to get around the problem
(removing the code-module from the startup form, setting HasModule to
No, save it, and adding the code-module back). The "workaround"
repairs the problem. This is good. But the problem keeps coming back
everyday. Seem like the problem returns whenever I have changed
something in the code module of the startup form. Is there a
"true-fix" to this problem?

Thanks in advance for any problem.

Jay Chan

 

[Albert D. Kallal]

Have you tried doing a save and compile all?

Can you create a mde file, and does that also not work?

Also, when it "fails", do you get some kind of error message?

So, I would try the first two suggestions above, and see what happens.

Also, does the start-up form have some code that runs?

 

[Jay Chan]

Have you tried doing a save and compile all?

I have not tried these. I will try it now and see if the problem will
stop coming back.

Can you create a mde file, and does that also not work?

What's "MDE" file? How do I create it from my "MDB" file? Do you mean
I should create a "MDE" file from the "MDB" file when I encounter the
problem?

Also, when it "fails", do you get some kind of error message?

No error message. I got a window with something like a MS-Access style
pop-down menu at the top, and with a blank "client-area". When I
clicked at the [x] box at the upper right corner of the window, the
window would disappear and then I would see a similar looking window
showing on the screen. At that point, the window will not respond. I
would need to terminate it using Windows Tasks Manager.

Also, does the start-up form have some code that runs?

Yes, the start-up form has a code module, and the code module has
programs in it.

Thanks.

Jay Chan

 

[Albert D. Kallal]

I have not tried these. I will try it now and see if the problem will
stop coming back.


What's "MDE" file? How do I create it from my "MDB" file? Do you mean
I should create a "MDE" file from the "MDB" file when I encounter the
problem?

A mde file is a ms-access program where all the code has been compiled and
then the source code has been removed. This means that your users cannot
modify forms, reports, or even view/see the original code you wrote.
virtually all software you purchase for your computer has been complied, and
the original source code has been removed. Since now YOU ARE the software
developer, then you can / should do the same right BEFORE your deploy your
application. This does mean you keep the original mdb file for development
purposes, as it is requited to create/make changes. You should also consider
spitting your program code/forms out of the data.

For more info on this, check out:
http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm

Yes, the start-up form has a code module, and the code module has
programs in it.

So, I would hold down the shift key during start-up to NOT run your start-up
form. You then can simply run/check/change/design/debug that problem form.
In other words you can try running the form by doubling clicking on it. I
would remove the start-up form specification in the tools-start-up until you
get the form working. Likely the problem is the code that you trying to run
in the module.