Extremely advanced user in VBA to newbie in VB -- Please help!
Shaka215
using VBA.. I am very comfortable and confindent at what I can do with
Excel and VBA -- however I would like to cross this bridge of calling
*.xls programs -- to being actual *.exe programs.
Does anyone have any good sources for information on how to
transistsion from using Excel as a database into using VB? I know SQL
and databases -- just don't understand how to build internal databases
with VB and have it refrence that data -- like say I could inside of
Excel...
UserForm1.TextBox1.Value = Sheets("Sheet1").Range("A2").Value
Range A2 Value =Vlookup(A1, Sheet1!A:IV, 2, False)
If I can learn how to basically VBA Vlookup "formula" inside of VB I'd
be in good shape to learn other things -- as this was the foundation I
started with Excel.
Any help is going to be tremendous!! Thanks!
thomas...@gmx.at
> Hi! I am an extremely advanced user at programming inside of MS Excel
> using VBA.. I am very comfortable and confindent at what I can do with
> Excel and VBA -- however I would like to cross this bridge of calling
> *.xls programs -- to being actual *.exe programs.
>
> Does anyone have any good sources for information on how to
> transistsion from using Excel as a database into using VB?
There is a group about visual basic at comp.lang.basic.visual
which could probably be more helpful.
Greetings Thomas Mertes
Seed7 Homepage: http://seed7.sourceforge.net
Seed7 - The extensible programming language: User defined statements
and operators, abstract data types, templates without special
syntax, OO with interfaces and multiple dispatch, statically typed,
interpreted or compiled, portable, runs under linux/unix/windows.
ep...@juno.com
The short answer is that you can not really do the same things in VB
as you can in VBA. In VB you don't have an Excel application or a
workbook or a worksheet to work with. [ignoring office automation].
The object model is different. In ordinary VB, VB is the host
application. So you use ordinary variables and arrays to hold values.
Also naming convetions are different for controls.
for example:
dim x, y as single
x = Value(Text1.text)
y = Value(Text2.text)
Text3.text = Str(x + y)
etc.
HTH
In this respect, VB is more like the older, traditional forms of Basic
customarily discussed in this newsgroup.
- e
David Williams
-> customarily discussed in this newsgroup.
Talking about older BASICs, I have made an observation...
A while ago, I posted here a QBasic program I had written that
calculates the position of the sun in the sky as seen from anywhere on
Earth at any time on any date, and also the required alignment of a
mirror if it is to reflect sunlight in any desired direction. I also
posted (and several people here tested for me) a "dumbed-down" version
that would run in ancient BASICs such as GW-BASIC, and also in some
recent implementations that are compatible with old BASICs. This
version of the program even has line numbers!
I also posted the same two versions on a couple of websites that are
concerned with solar energy. These sites keep count of the number of
times each posting is accessed, so I can see how many times each of the
two versions has been read. Possibly, some of these times, the program
has been copied and maybe put to use.
The interesting thing is that the dumbed-down version gets read far
more often than the QBasic one, by a ratio of about 2 to 1. Apparently,
in this context, there's a lot more interest in code that will work on
old BASICs than in more elegant, better-documented code.
Interesting...
dow