>Hi All,
>
> Just to let you know that I have deleted the download I posted a few months ago, which to allowed you to Zip/Unzip from within VFP using just the built in code of Windows XP. If anyone has downloaded it, please be aware of some licencing issues.
>
> I have received an email today from Glen Horton of InnerMedia. It seems that when MS licenced the Zip bits in XP, it did not include rights for users to use the facilities directly outside of XP. I reproduce his email below.
>
> Makes you wonder what other licences are needed whenever we step out of straight VFP. Does MS publish a list of which bits are freely usable?
>
>Alan
>
>

>Hello Alan,
>
>I was very surprised to see your inventive approach to using the Windows XP
>zip folders facilities from VFP and I want to take this opportunity to let
>you know of some legal ramifications related to the approach you have
>developed.
>
>Third-party sub-licensing for using the Windows XP Shell zip folders via
>programatic or automated means is not covered by Microsoft's DynaZip
>license.  To use DynaZip's facilities and programatic interfaces either
>directly or indirectly, a developer must have a valid, legal license to
>DynaZip.  Please warn your readers that they will be exposed legally if
>they intend to use the Windows XP zip folders facilities via programatic
>or automated means without acquiring a license.
>
>If you need additional information regarding DynaZip Licensing, please
>contact me.
>
>Thanks,
>
>
>Glen Horton
>Voice: 978-448-9484 (US Eastern Time Zone)
>email: mailto:gh@innermedia.com
>
>

Hi Alan,

I am not quite sure I understand where are those "DynaZip's facilities and programatic interfaces" that you had used in your solution.

I cannot see any of them:
- shell.application - it is the Windows scripting interface
- the zip newscripting file designator/header is documented in the registry: it is still Windows Scripting. If the file header string is something that is related to Dynazip, then you can create manually empty zip file and use it as a template in the project. This approach does not require knowledge or usage of the header.
- all other stuff, like Namespace and copyhere, - they are not a "DynaZip facilities", but Windows Scripting interface.

Additionally, the approach you had used is widely published; there are tons of examples written in C, Excel VBA, .NET, Scripting and widely published on the forums.

Also, in the .NET there is the PACKAGING class that is part of the System.IO. And the .NET documentation does not mention that it is
"DynaZip's facility or programatic interface".

I believe that though we need to respect Glen's opinion, until he does not point exactly what are "DynaZip's facilities and programatic interfaces" and where it is noted in the Windows EULA, we are allowed to use Windows Interface and facilities under the agreement between the MS and the developer. In any case while using Windows we do not have agreement with DynaZip.