#VBMuscle question
3 messages in this thread
Mark, I'm definitely going to buy VBMuscle soon, but I must wait until the
next paycheck comes in and I can pare down my MasterCard balance some. I
do have a question about VBMuscle that I like answered (please!).
You have a wonderful routine to pop up a dialog box for opening files. I
assume it works as easily as the form that came with VBTools (I've looked
at the demo of VBMuscle, but this does not tell me the calling sequence).
Anyway, can you set a flag to allow/disallow whether the user can change
the 'pattern' (*.doc for example)? I sometimes do not want the user to
attempt to open a file without the appropriate extension. This is
something I put in my own file open form (pre VBTools) and would like this
in the future.
Maybe I'm the only one that wants this feature and maybe it's too late
anyway, but there it is, do what you want with it.
Thanks for VBTools and VBMuscle and the opportunity to 'beta' one of your
products. I'm glad for the opportunity to do this, since I'm not GE or
EXXON or some HUGE client that usually gets these privileges from Lotus or
MS or Borland!!!!!!!!!!!!!!
Keep up the GREAT WORK!
Bruce
There is 1 Reply.
Bruce,
Thanks for your kind words! I'll leave you a private message showing you
how the call is set up.
The routine does not have the feature you describe. Please keep in mind
that this routine was written by Microsoft (not us) – we've provided a
"wrapper" around the routine so you can get the full functionality that was
intended. For this routine in particular, that means being able to pop up a
help screen when the user clicks the help button. (We also set things up so
you don't need to worry about pointers!)
Having said that, it's a simple matter for you to check the extension when
the routine returns. One of the values we pass back to you is exactly where
in the file name the extension begins. If the user types one that you don't
want, simply MsgBox him and recall the routine!
Mark
There is 1 Reply.
Bruce,
Well, we modified the control so that when StateButton = True, it will
revert to the pre-push state if you release the button when the mouse
pointer is *off* the control.
The new VBX files will be available tomorrow from our BBS.
Thanks for reporting the problem!
Mark