R
Ronald Dodge
As I was just doing a test run with one of my date fields, I ran into an
ambiguity with the aDialogColor picker as I attempted to change colors. I
have the command button tool and the Calendar tool from Leban's web site.
Once I ran into the bug and noticed the line it was on (had to move the VB
Editor to see it), I click on reset, then the code went into an inifinite
recursive loop. I attempted to Ctrl-Break out of the code, but it just
wouldn't come out of it. Eventually, I ended up ending the program, though
it was wierd how that happened cause I pressed Ctrl-Break repeatedly and
fast which then the application quit on me after me hitting this about 3
times successively fast.
I reopened the file, looked for the functions, which then found them in the
modcmdbuttonver1 and modcolorpicker modules. I looked to see if there was a
difference between the 2, of which there was a bit of a difference, but
didn't spend the time to determine what it did differently, but rather just
prequalified the function call to the appropriate module that each function
call was intended to call on.
This is basically how I decided to resolve the issue and thought it was the
best way, especially since I don't like to leave code to ambiguity given the
experience that I ran into within Excel's VBA when I first started to work
with VBA 4.5 years ago.
ambiguity with the aDialogColor picker as I attempted to change colors. I
have the command button tool and the Calendar tool from Leban's web site.
Once I ran into the bug and noticed the line it was on (had to move the VB
Editor to see it), I click on reset, then the code went into an inifinite
recursive loop. I attempted to Ctrl-Break out of the code, but it just
wouldn't come out of it. Eventually, I ended up ending the program, though
it was wierd how that happened cause I pressed Ctrl-Break repeatedly and
fast which then the application quit on me after me hitting this about 3
times successively fast.
I reopened the file, looked for the functions, which then found them in the
modcmdbuttonver1 and modcolorpicker modules. I looked to see if there was a
difference between the 2, of which there was a bit of a difference, but
didn't spend the time to determine what it did differently, but rather just
prequalified the function call to the appropriate module that each function
call was intended to call on.
This is basically how I decided to resolve the issue and thought it was the
best way, especially since I don't like to leave code to ambiguity given the
experience that I ran into within Excel's VBA when I first started to work
with VBA 4.5 years ago.