Mangesh,
Even launching Excel from VB, you still have Excel macro code, which is
against policy.
You will need all the code to reside in your VB app, no code associated with
Excel. You will have manipulate the Excel object model from outside (your VB
app) rather than inside (macro code).

Nick

"Mangesh Yadav" wrote in message
...
Carrying on from here.....

Lets say I have a VB application which launches my excel file. Now my
macros
mainly consist of
1. Event modules for each sheet.
2. User forms
3. UDFs
4. Standard modules

Suppose I want to protect my business logic (which resides in the standard
modules), one way is ofcourse to protect the VBA with the password (which
I
don't know how safe it is). But is there any way where I can convert these
modules into kind of executables so that the user cannot manipulate the
code
in these standard modules. And also allow the code to run on the click of
a
button in the worksheet as if I am running a standard macro.

Mangesh





"Bob Phillips" wrote in message
...
Mangesh,

Many system administrators will restrict the functions of products and
the
OS, so that the average user is functionally crippled, as part of
company
policy. Such restrictions include the ability to set date and time, to
add
system variables, etc., and within Excel to run macros by setting the
security setting to high and stopping the ability to change that.

In this instance, if you want to manipulate Excel spreadsheets via code,
I
think you will have to do it externally via automation. That is, create
an
application using an approved tool, such as VB, that uses Excel as a
server
app, and manipulates it from within your app. It is very
straight-forward,
the main learning exercise is to be aware of which object you are
addressing, and reference properly at all times.

Of course, this still leaves the problem that the user will not be able
to
install it, the CD drive will be disabled as well if not even sealed, so
you
will need the co-operation of the system administrators for that. They
might
say no, they might say yes but insist on testing it themselves, or they
might say yes. As you need their co-operation, you could also ask them
about
whether they would install a COM add-in, or a simple Excel add-in.
Whatever
way, your first action should be to discuss with them, otherwise you
might
just be wasting your time and effort.

--
HTH

Bob Phillips

"Mangesh Yadav" wrote in message
...
Hi Everyone,

I have a spreadsheet which uses macros extensively. Now if a
particular
company has a policy which does not allow macros, what is the
alternative
for my spreadsheet.

I know the question is bit unclear regarding the policies, but even I
don't
know how this is done. Another question I have is: when a particular
company
says that it does not allow macros, what is it that they do to prevent
the
user from allowing a macro to run. (Is it something like they disable
the
Tools Security feature...?)

Thanks in advance.

--
- Mangesh
------------------------------------------
Office XP & Windows XP