VBA modules(?)

  • Thread starter Thread starter Jack Marks
  • Start date Start date
J

Jack Marks

I just want to write a simple program, without using all of the capabilities
of VBA. So, on my program, I have Form 2 which has a (Command Button)?
which, when clicked, brings up Form 3. On Form 3, I have 2 more Command
Buttons, I want to do different things. So I want to write code, possibly
extensive code, for each command button. But instead, I am getting all
these module things popping up, which, all they are doing is confusing me.
I suppose they are there to help. Are they there to help? Can I live
without them? Just erase them and do everything from the code on the
command buttons like I want to do?
 
It is important that you understand the following:

1. I know BASIC. I have written lots and lots of programs in BASIC, for
years and years. You lay some code down, and it has lines and procedures
and stuff, and it does the job nicely.

2. Visual Basic has jillions of possibilities, but unfortunately does not
readily lend itself to just writing code like we used to do in real BASIC.
All I want to do is write the code. I want 2 buttons, see, and I want
lots of code under each button. Don't want no fancy method to file the
procedures. Just want to write code. But I keep running into these
obstacles, which have nothing to do with coding, but only with the program
(Visual Basic) itself.

3. I just completed a rather nice visual basic application which has one
Excel workbook read another and pick out important data. It works and
everyone likes it. Now I am trying to do a simple menu driven program in
the Visual Basic, no Excel involved at all, but one menu item brings up
procedures from other menu items, and I can't figure out why.
 
Jack: If you're "Now I am trying to do a simple menu driven program in
the Visual Basic, no Excel involved at all", then why are you in the Excel
newsgroups? You should be in the Visual Basic newsgroups. Don't confuse VBA
with VB. VBA is only a "child" of VB.
*******************
~Anne Troy

www.OfficeArticles.com
 
It is important that you understand the following:
Click to expand...

It's important that you understand the following:
1. I know BASIC. I have written lots and lots of programs in BASIC, for
years and years. You lay some code down, and it has lines and procedures
and stuff, and it does the job nicely.
Click to expand...

Apparently you don't just "lay some code down" or what you've written
would work, now, wouldn't it?
2. Visual Basic has jillions of possibilities, but unfortunately does not
readily lend itself to just writing code like we used to do in real BASIC.
All I want to do is write the code. I want 2 buttons, see, and I want
lots of code under each button. Don't want no fancy method to file the
procedures. Just want to write code. But I keep running into these
obstacles, which have nothing to do with coding, but only with the program
(Visual Basic) itself.
Click to expand...

As Anne pointed out, it sounds as though you know less about VBA than
you think you do.
3. I just completed a rather nice visual basic application which has one
Excel workbook read another and pick out important data. It works and
everyone likes it. Now I am trying to do a simple menu driven program in
the Visual Basic, no Excel involved at all, but one menu item brings up
procedures from other menu items, and I can't figure out why.
Click to expand...

Are you sure everyone likes it? Or are they just saying that they
like it so that you'll feel good?

Try pressing F1 and spending some time there.

Or perhaps I could recommend lesson one:
http://www.vbaexpress.com/training/lesson01.htm

MP-
 
Back
Top