Mike,

for 1., there is no "best practice" I guess. Whether you need one or more
modules is just a matter of organisation. It doesn't change the behaviour of
the program at all.
For 2., the functions of Excel are not included since Excel is a separate
program. However, you may use Excel from VB using automation. That is,
creating a reference to Excel in VB and refer to its objects, methods and
properties. But Excel still has to be on the target machine.

Hope this helps you getting started.

Stefan

"Mike Iacovou" schrieb im
Newsbeitrag ...
OK. I think i know someone with VS6... going to attempt to convert VBA to
a VB project (VB 6 for ease). I have some basic questions to ask please:

1. The current system has code across a number of modules etc - do i just
paste all the code into a single text file to import into studio & then
correct it's references / syntax, or will there be a clever "import VBA"
option in studio ?
2. The Excel functions used in the workbook - are they included / similar
in VB 6 ie can this code run WITHOUT Excel present on the system - or are
the advanced filters etc etc functions only part of Excel ? If the latter,
are there any developer code etc that can be used with permission etc to
create a standalone app ?

These 2 questions will help shape the path - and in about 3 years i'll
have i done !!!
thanks again.