By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,495 Members | 1,110 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,495 IT Pros & Developers. It's quick & easy.

A97: Is it a feature or a beature of Access compiling code on the clipboard?

P: n/a
MLH
I had a form (Form12) with a code error in it. I knew it was there. I
even planned on fixing it (someday). I needed a comprehensive test
of all my code so I clicked Debug, Compile All Modules. My standard
modules were all good but the compilation test halted in a Class
Module on Form12 due to the error. OK, I thought, don't really
wanna screw around with this right now, so I'll take it out-a-the
equation. I chose it on the database window and typed CTRL-x.
Then, I restarted the Compile All Modules process. You can
guess what happened...

Compile error in hidden module: Form_~TMPCLP506991

There was a HELP button in the error msgbox. Here's what
the HELP had to say...

Compile error in hidden module: <module name>
Specifics
A protected module can't be displayed. This error has the following
cause and solution: There is a compilation error in the code of the
specified module, but it can't be displayed because the project is
protected. Unprotect the project, and then run the code again to view
the error. For additional information, select the item in question and
press F1.

If this is a Feature, then its buggy because Access terminates if
you CUT something else to the clipboard whilest the error is being
reported (IE, the HELP text above) then click the error msgbox's
OK button. The form object on the clipboard has been replaced by
some text and Access becomes confused. Has this behavior been
rectified in the 3 advanced versions of MS Access since 97?
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Sun, 24 Jul 2005 08:40:09 -0400, MLH <CR**@NorthState.net> wrote:
I had a form (Form12) with a code error in it. I knew it was there. I
even planned on fixing it (someday). I needed a comprehensive test
of all my code so I clicked Debug, Compile All Modules. My standard
modules were all good but the compilation test halted in a Class
Module on Form12 due to the error. OK, I thought, don't really
wanna screw around with this right now, so I'll take it out-a-the
equation. I chose it on the database window and typed CTRL-x.
Then, I restarted the Compile All Modules process. You can
guess what happened...

Compile error in hidden module: Form_~TMPCLP506991

There was a HELP button in the error msgbox. Here's what
the HELP had to say...

Compile error in hidden module: <module name>
Specifics
A protected module can't be displayed. This error has the following
cause and solution: There is a compilation error in the code of the
specified module, but it can't be displayed because the project is
protected. Unprotect the project, and then run the code again to view
the error. For additional information, select the item in question and
press F1.

If this is a Feature, then its buggy because Access terminates if
you CUT something else to the clipboard whilest the error is being
reported (IE, the HELP text above) then click the error msgbox's
OK button. The form object on the clipboard has been replaced by
some text and Access becomes confused. Has this behavior been
rectified in the 3 advanced versions of MS Access since 97?


not sure of the details but Access ofter leaves temporary things around
after you've deleted them, easiest is to close Access and reopen it,
or if you are in code always worth refreshing the relevant collection.

Nov 13 '05 #2

P: n/a
MLH
It certainly does leave things lying around.

This one's actually on the clipboard though, as you might guess
from its object name: Form_~TMPCLP506991
I've proven that, replacing the clipboard contents by cutting or
copying something else from another application to the clipboard
a during the reporting of the error. And, of course, CTRL-x cuts 'n
pastes to the Windows clipboard as a system default behavior.

not sure of the details but Access ofter leaves temporary things around
after you've deleted them, easiest is to close Access and reopen it,
or if you are in code always worth refreshing the relevant collection.


Nov 13 '05 #3

P: n/a
MLH <CR**@NorthState.net> wrote in
news:go********************************@4ax.com:
I had a form (Form12) with a code error in it. I knew it was
there. I even planned on fixing it (someday). I needed a
comprehensive test of all my code so I clicked Debug, Compile All
Modules. My standard modules were all good but the compilation
test halted in a Class Module on Form12 due to the error. OK, I
thought, don't really wanna screw around with this right now, so
I'll take it out-a-the equation. I chose it on the database window
and typed CTRL-x. Then, I restarted the Compile All Modules
process. You can guess what happened...
The compiled code is not gone until you compact the database.

[]
If this is a Feature, then its buggy because Access terminates if
you CUT something else to the clipboard whilest the error is being
reported (IE, the HELP text above) then click the error msgbox's
OK button. The form object on the clipboard has been replaced by
some text and Access becomes confused. Has this behavior been
rectified in the 3 advanced versions of MS Access since 97?


Comment out the offending line in the uncompilable form.

I have a particular comment that I use as a marker for "this needs
to be re-visited and fixed" so I can search an entire project and
find all the things I left needing fixing later.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #4

P: n/a
MLH <CR**@NorthState.net> wrote in
news:cd********************************@4ax.com:
It certainly does leave things lying around.

This one's actually on the clipboard though, as you might guess
from its object name: Form_~TMPCLP506991
I've proven that, replacing the clipboard contents by cutting or
copying something else from another application to the clipboard
a during the reporting of the error. And, of course, CTRL-x cuts
'n pastes to the Windows clipboard as a system default behavior.


Why are you hitting COMPILE ALL when you just want to COMPILE?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #5

P: n/a
David W. Fenton wrote:
Comment out the offending line in the uncompilable form.

I have a particular comment that I use as a marker for "this needs
to be re-visited and fixed" so I can search an entire project and
find all the things I left needing fixing later.


I just use:

' TODO:

--
[OO=00=OO]
Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.