|
-
Dec 3rd, 2003, 04:34 PM
#1
Thread Starter
Hyperactive Member
 Why compile VBA code in Access?
In Access 2000's Visual Basic design environment, what is the purpose/advantage of doing a Debug - Compile?
Are there any DISadvantages?
I tried this on a project with a bunch of modules, classes and code modules behind forms, and it took about 1 second!
The project is a bit larger but doesn't appear any faster.
Thanks, DaveBo
Last edited by DaveBo; Dec 3rd, 2003 at 04:46 PM.
"The wise man doesn't know all the answers, but he knows where to find them."
VBForums is one place, but for the really important stuff ... here's a clue 1Tim3:15
-
Dec 4th, 2003, 07:58 AM
#2
Lively Member
It can help to identify compiling errors and some run-time errors especially if you use the Option Explicit directive ...
-
Dec 8th, 2003, 10:19 AM
#3
Thread Starter
Hyperactive Member
Been using it
Well, it doesn't seem to have any disadvantages
and it does catch some coding errors.
It also apparently has nothing to do with making MDE files, so nothing is "lost".
"The wise man doesn't know all the answers, but he knows where to find them."
VBForums is one place, but for the really important stuff ... here's a clue 1Tim3:15
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote