Code Jumps

E

eggpap

I have a wb with many UDFs and sheets, modules, forms etc.
When I use the step by step debug (F8 key), sometimes the step don'
jumps to the following statement of the routine but to some statement o
a UDF. I'ld like to know if this is a correct behaviour or it's a sig
of some defects hidden in the procedure.

Apart these jumps that I see only debugging, apparently the procedur
performs correctly. I'ld like, however, to know if these jumps must (o
can) be avoided. I thought, for example, to place a pair o
Application.EnableEvents (False/True) at the beginning and at the end o
every routine/function, but I am not sure.

Thanks,
Emilian
 
K

Kassie

Not knowing your code makes it impossible to answer! It might just be that
your code actually calls the UDF?
 
E

eggpap

Thanks for your reply,

Kassie;181879 said:
Not knowing your code makes it impossible to answer! It might just b
that
your code actually calls the UDF?

No, the UDFs are called by Excel itself not by code.
I think you can reply without seeing the code, that is very big. I as
only if you, thanks to the experience I don't have, have ever seen
similar behaviour.

Emilian
 
S

Simon Lloyd

Emiliano, attach a workbook so we can see whats going on and help yo
further

Attatchments.

To upload a workbook, click reply then add your few words, scroll dow
past the submit button and you will see the Manage Attatchments button
this is where you get to add files for upload, if you have any troubl
please use this link or the one at the bottom of th
any page.
Thanks for your reply


Quote
Originally Posted by *Kassie* '[image
http://www.thecodecage.com/forumz/images/tz/buttons/viewpost.gif]
(http://tinyurl.com/8hkanq)
-Not knowing your code makes it impossible to answer! It might just b
tha
your code actually calls the UDF?

No, the UDFs are called by Excel itself not by code
I think you can reply without seeing the code, that is very big. I as
only if you, thanks to the experience I don't have, have ever seen
similar behaviour.

Emilian

--
Simon Lloy

Regards,
Simon Lloyd
'The Code Cage' (http://www.thecodecage.com
 
E

eggpap

Thanks,

my wb links to many mdb files. To get it correctly perfoming you nee
all the files installed on a test folder named as you like. Moreover,
use Excel 2003 Italian version, probably you'll have some problem o
function convertion.

Emilian

+-------------------------------------------------------------------
|Filename: CCtest.zip
|Download: http://www.thecodecage.com/forumz/attachment.php?attachmentid=63
+-------------------------------------------------------------------
 
J

Jim Thomlinson

As a guess you are using the UDF within your workbook somewhere. While your
code is executing a change is made to your workbook which forces a
calculation. When the calculation runs your UDF gets called as the cell the
udf is in has been dirtied by some sort of action of the UDF has been defined
as Volatile...
 
E

eggpap

When the calculation runs your UDF gets called as the cell the
udf is in has been dirtied by some sort of action of the UDF has bee
defined
as Volatile...

I think, but I'm not sure for my bad english, that this is an anorma
situation. How to define Volatile an UDF action? May I find mor
information on this? Have you seen my workbook?

Thanks, Emilian
 
S

Simon Lloyd

I had asked someone Italian to look at your workbook to help, howeve
your VBA Project is password protected so they couldn't view your code

eggpap;182247 said:
I think, but I'm not sure for my bad english, that this is an anorma
situation. How to define Volatile an UDF action? May I find mor
information on this? Have you seen my workbook

Thanks, Emilian

--
Simon Lloy

Regards,
Simon Lloyd
'The Code Cage' (http://www.thecodecage.com
 
S

Simon Lloyd

eggpap, we're glad you have it solved, why not share the method by whic
you solved it, it may help others in the future

Once you have finished with this threa

--
Simon Lloy

Regards,
Simon Lloyd
'The Code Cage' (http://www.thecodecage.com
 
Top