run VBA code in something other than debug mode?

[Marie]

I'm a VB programmer that just inherited an ex-coworker's Access VBA program.
It runs incredibly slow, and I'd like to speed it up, but I understand you
can't just build an executable in Access like you can in VB. What are my
options here? Build a VB front-end and make an executable from that?

Thanks,
marie

[Amhed the Head]

"Marie" <Ma*******@mbg.com> wrote in message
news:11*************@corp.supernews.com...

I'm a VB programmer that just inherited an ex-coworker's Access VBA
program. It runs incredibly slow, and I'd like to speed it up, but I
understand you can't just build an executable in Access like you can in
VB. What are my options here? Build a VB front-end and make an executable
from that?

Thanks,
marie

Is not VBA sweetie! Is your app as an MDB? Yes? Then make into MDE! If
that be no help then you have db designed by monkey! You go make FE in VB
executable and you finish in 3 years sweetie!

[Tommy T-Bag]

Similarly, if it is an .ADP you can make it an .ADE.
Tools > Database Utilities > Make .ADE File
Will remove all code modules and keep it from becoming decompiled.

[Trevor Best]

Tommy T-Bag wrote:

Similarly, if it is an .ADP you can make it an .ADE.
Tools > Database Utilities > Make .ADE File
Will remove all code modules and keep it from becoming decompiled.

Compiled or not, wouldn't make such a difference to make someone comment
on it being "incredibly slow", making an incredibly slow MDB into an MDE
will result in an incredibly slow MDE.

Amhed the Head could be right about the monkey. In Marie's place I'd
start looking at what is holding up the application, could be the data
access or just badly written code. OTOH it could be that the application
is doing that much work that it just takes that long.