>>>>Thanks for the suggestions. I will use them to see if I can squeeze it further.
>>>>
>>>>Using Crystal reports for reporting doesn't help as far as the install file size is concerned.
>>>>
>>>>Cyril.
>>>
>>>I see - that would inflate it quite a bit (although I have no idea how much). Is it possible to separate the C.R. runtime, so that only those who don't have it installed already have to download it? Or even redirect them to the Web site for this part?
>>>
>>>I hope I am not suggesting anything illegal; I am not sure about the legal implications in this case.
>>
>>I did some tests and this is how it looks:
>>
>>

>>Application and data files:    8 mB
>>Help and PDF files:            3 mB
>>FoxPro runtime files:          7 mB
>>Crystal report runtime files: 10 mB
>>Total:                        28 mB
>>

>>
>>The Crystal part is a big chunk. I am thinking now of having two downloads, with and without reporting capability. The question now is would a 28mb download put people off, whereas they wouldn’t mind an 18mb download??
>>
>>Or doesn’t it matter at these sort of file sizes...
>
>It depends on the group you're targeting. If they all have broadband connections, then they won't bother too much.
>
>But I'm quite amazed about the size of your components. Can things be squeezed? Personally, I use InnoSetup. It squeezes automatically. Are all files really necessary? For example, what are the components of your foxpro runtime files?
>
>On my own website you'll find another trialware ap, built in vfp. I thought mine was big, but yours is extreme. :)

I envy your 5mB<g>.

I don't see a list of all the files that are installed in your application. Is everything in C:\Program Files\ClickWork, or is something also installed in Windows\System32?

I am using Wise Installation System which puts in the run times needed automatically. I will do a file by file check to see what can be removed.

Cyril.