Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > microsoft.public.excel.programming > #108239 > unrolled thread

Re: Better protection for VBA project?

Back to article view | Back to microsoft.public.excel.programming

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Better protection for VBA project? pbarwaliya@gmail.com - 2015-11-27 04:19 -0800
    Re: Better protection for VBA project? GS <gs@v.invalid> - 2015-11-27 12:42 -0500
      Re: Better protection for VBA project? witek <witek7205@gazeta.pl.invalid> - 2015-11-27 15:10 -0600
        Re: Better protection for VBA project? GS <gs@v.invalid> - 2015-11-27 16:28 -0500
          Re: Better protection for VBA project? witek <witek7205@gazeta.pl.invalid> - 2015-11-27 16:53 -0600
            Re: Better protection for VBA project? GS <gs@v.invalid> - 2015-11-27 19:16 -0500
              Re: Better protection for VBA project? witek <witek7205@gazeta.pl.invalid> - 2015-11-27 20:50 -0600
                Re: Better protection for VBA project? GS <gs@v.invalid> - 2015-11-27 22:01 -0500
                  Re: Better protection for VBA project? witek <witek7205@gazeta.pl.invalid> - 2015-11-28 01:11 -0600
                    Re: Better protection for VBA project? GS <gs@v.invalid> - 2015-11-28 02:14 -0500
                      Re: Better protection for VBA project? witek <witek7205@gazeta.pl.invalid> - 2015-11-28 01:37 -0600
                        Re: Better protection for VBA project? GS <gs@v.invalid> - 2015-11-28 10:38 -0500
                          Re: Better protection for VBA project? witek <witek7205@gazeta.pl.invalid> - 2015-11-28 14:37 -0600

#108239 — Re: Better protection for VBA project?

hi,
 
I have tried JKP process and it works but my file contains web quires and when  try to run it shows runtime error 1004 is there any solution for this?

regards,

Prashant   

[toc] | [next] | [standalone]

#108240

> hi,
>  
> I have tried JKP process and it works but my file contains web quires 
> and when  try to run it shows runtime error 1004 is there any 
> solution for this?
>
> regards,
>
> Prashant   

Unviewable+
It's not free!

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#108241

GS wrote:
>
> Unviewable+
> It's not free!
>
Did you have a case when it did not work?

[toc] | [prev] | [next] | [standalone]

#108242

> GS wrote:
>>
>> Unviewable+
>> It's not free!
>>
> Did you have a case when it did not work?

No cases that I'm aware of!

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#108243

GS wrote:
>> GS wrote:
>>>
>>> Unviewable+
>>> It's not free!
>>>
>> Did you have a case when it did not work?
>
> No cases that I'm aware of!
>


Thanks
I will try it.
I do no need anything more just VBA protection.

[toc] | [prev] | [next] | [standalone]

#108244

> GS wrote:
>>> GS wrote:
>>>>
>>>> Unviewable+
>>>> It's not free!
>>>>
>>> Did you have a case when it did not work?
>>
>> No cases that I'm aware of!
>>
>
>
> Thanks
> I will try it.
> I do no need anything more just VBA protection.

It doesn't do anything else. It renders the same 'effect' as JKP's 
shared workbook trick, (which as you probably know can be undone) by 
altering the binary at various levels. Only admitted flaw to date is 
that if you use the 'optional' advanced protection it loses a level 
when you save your file. IMO, that degree of protection is overkill 
anyway and so i not an issue with me!<g>

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#108245

GS wrote:
>> GS wrote:
>>>> GS wrote:
>>>>>
>>>>> Unviewable+
>>>>> It's not free!
>>>>>
>>>> Did you have a case when it did not work?
>>>
>>> No cases that I'm aware of!
>>>
>>
>>
>> Thanks
>> I will try it.
>> I do no need anything more just VBA protection.
>
> It doesn't do anything else. It renders the same 'effect' as JKP's
> shared workbook trick, (which as you probably know can be undone) by
> altering the binary at various levels. Only admitted flaw to date is
> that if you use the 'optional' advanced protection it loses a level when
> you save your file. IMO, that degree of protection is overkill anyway
> and so i not an issue with me!<g>
>
It did not work. pivot tables, external data. I do not remember exactly 
why I couldn't use it.

[toc] | [prev] | [next] | [standalone]

#108246

> GS wrote:
>>> GS wrote:
>>>>> GS wrote:
>>>>>>
>>>>>> Unviewable+
>>>>>> It's not free!
>>>>>>
>>>>> Did you have a case when it did not work?
>>>>
>>>> No cases that I'm aware of!
>>>>
>>>
>>>
>>> Thanks
>>> I will try it.
>>> I do no need anything more just VBA protection.
>>
>> It doesn't do anything else. It renders the same 'effect' as JKP's
>> shared workbook trick, (which as you probably know can be undone) 
>> by
>> altering the binary at various levels. Only admitted flaw to date 
>> is
>> that if you use the 'optional' advanced protection it loses a level 
>> when
>> you save your file. IMO, that degree of protection is overkill 
>> anyway
>> and so i not an issue with me!<g>
>>
> It did not work. pivot tables, external data. I do not remember 
> exactly why I couldn't use it.

My understanding is that the latest release of unviewable+ 'just 
works'! I don't use it myself but I've done extensive work with another 
monitor of these NGs (who is a MVP I will not name). I do know the 
issues you cite are common with shared workbooks and so I suspect any 
methodology that messes with anything to do with that feature will 
cause trouble.

Of course, there's always the option to go DLL or COMAddin!

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#108252

GS wrote:
> Of course, there's always the option to go DLL or COMAddin!

I did it about 7 years ago.
I moved all calculation logic to C++
Unfortunately a couple of things must stay in VBA or we simply do not 
want client to add anything to VBA.

What I do is more like document facing project . File can be send around 
the world.
I can't install anything. All VSTO or DLL requiring registration with 
admin right can't be used.

[toc] | [prev] | [next] | [standalone]

#108253

> GS wrote:
>> Of course, there's always the option to go DLL or COMAddin!
>
> I did it about 7 years ago.
> I moved all calculation logic to C++
> Unfortunately a couple of things must stay in VBA or we simply do not 
> want client to add anything to VBA.
>
> What I do is more like document facing project . File can be send 
> around the world.
> I can't install anything. All VSTO or DLL requiring registration with 
> admin right can't be used.

Not even if your installer runs with elevated permissions?

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#108254

GS wrote:
>> GS wrote:
>>> Of course, there's always the option to go DLL or COMAddin!
>>
>> I did it about 7 years ago.
>> I moved all calculation logic to C++
>> Unfortunately a couple of things must stay in VBA or we simply do not
>> want client to add anything to VBA.
>>
>> What I do is more like document facing project . File can be send
>> around the world.
>> I can't install anything. All VSTO or DLL requiring registration with
>> admin right can't be used.
>
> Not even if your installer runs with elevated permissions?
>

Clients do not have rights to install anything.
They work on virtual desktops and every time they login they see brand 
new computer. Nothing stays except data on shared drives.

They other reason is that they do not want to install anything.
They want to open excel file, do their work and send that file to 
another person.
I call that iPhone syndrome.  One button click and nothing more advanced.

[toc] | [prev] | [next] | [standalone]

#108262

> GS wrote:
>>> GS wrote:
>>>> Of course, there's always the option to go DLL or COMAddin!
>>>
>>> I did it about 7 years ago.
>>> I moved all calculation logic to C++
>>> Unfortunately a couple of things must stay in VBA or we simply do 
>>> not
>>> want client to add anything to VBA.
>>>
>>> What I do is more like document facing project . File can be send
>>> around the world.
>>> I can't install anything. All VSTO or DLL requiring registration 
>>> with
>>> admin right can't be used.
>>
>> Not even if your installer runs with elevated permissions?
>>
>
> Clients do not have rights to install anything.
> They work on virtual desktops and every time they login they see 
> brand new computer. Nothing stays except data on shared drives.
>
> They other reason is that they do not want to install anything.
> They want to open excel file, do their work and send that file to 
> another person.
> I call that iPhone syndrome.  One button click and nothing more 
> advanced.

Yes, I get that. My solution for portable apps (run from USB drive) is 
to run DLLs reg-free via LoadLibrary(). No reason you can't do same 
other than it requires you ship the DLL with your workbook. This 
clearly won't work in your scenario!

Perhaps you can have someone using a current release unviewable+ lock 
your VBA project so you can give it a test drive!?

-- 
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
  comp.lang.basic.visual.misc
  microsoft.public.vb.general.discussion

[toc] | [prev] | [next] | [standalone]

#108264

GS wrote:
>> GS wrote:
>>>> GS wrote:
>>>>> Of course, there's always the option to go DLL or COMAddin!
>>>>
>>>> I did it about 7 years ago.
>>>> I moved all calculation logic to C++
>>>> Unfortunately a couple of things must stay in VBA or we simply do not
>>>> want client to add anything to VBA.
>>>>
>>>> What I do is more like document facing project . File can be send
>>>> around the world.
>>>> I can't install anything. All VSTO or DLL requiring registration with
>>>> admin right can't be used.
>>>
>>> Not even if your installer runs with elevated permissions?
>>>
>>
>> Clients do not have rights to install anything.
>> They work on virtual desktops and every time they login they see brand
>> new computer. Nothing stays except data on shared drives.
>>
>> They other reason is that they do not want to install anything.
>> They want to open excel file, do their work and send that file to
>> another person.
>> I call that iPhone syndrome.  One button click and nothing more advanced.
>
> Yes, I get that. My solution for portable apps (run from USB drive) is
> to run DLLs reg-free via LoadLibrary(). No reason you can't do same
> other than it requires you ship the DLL with your workbook. This clearly
> won't work in your scenario!

Aplication.RegisterXLL
It solves a lot of problems with complicated calculation processes and 
does not require any registration.


>
> Perhaps you can have someone using a current release unviewable+ lock
> your VBA project so you can give it a test drive!?
>
I will try it when I find a minute free time.

[toc] | [prev] | [standalone]

Back to top | Article view | microsoft.public.excel.programming

csiph-web