Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Why is accessing APP.MAJOR taking a long time?

0 views
Skip to first unread message

Joker

unread,
Jan 10, 2001, 10:42:58 AM1/10/01
to

Anyone know why a command like this would take a long time to execute?

lblVerstion = "Version: " & app.marjor & "." & app.minor


I've tried:
-- separating the code into multiple lines.
-- Assigning to a variable instead of a label
-- Putting DoEvents between multiple lines.
-- Putting the code in a timer - (hoping for some multitasking)

The problem is that I have a splash screen and want to put the program
version on there. But I also want the screen to come and up and display
quickly, so the user knows that something is happening. When I include any
code that references APP.MAJOR or APP.MINOR there is a pretty long delay at
that point. As soon as I remove the code, everything else runs quickly.

Also note: It runs just fine (fast) in the development environment. It's
only in the compiled EXE that it runs slowly.

J French

unread,
Jan 11, 2001, 5:35:29 AM1/11/01
to
My gues is that it is because it is looking into the EXE on disk

disk access eats time.

How about putting up the splash screen and filling in a few bits of
info later - it might look quite neat.

On Wed, 10 Jan 2001 15:42:58 GMT, "Joker" <jabad...@hotmail.com>
wrote:

0 new messages