In this case I would suggest to include the older version in a subfolder in the same ZIP with corresponding readme.
>Nick,
>
>What if the current version of a download was not backward compatible and the user only had the older version of Foxpro. Would it have been ok if John had defined it as a new version?
>
>Renoir
>
>>We prefer to keep the zip filename the same. The information about the particular version typically should be contained inside the ZIP, (readme, file timestamp, etc.)
>>
>>>Forget the 'sidefonts-a.zip', they renamed it back to 'sidefonts.zip', but it's the new one and now available for download.
>>>
>>>Enjoy!
>>>
>>>
>>>>Hey UT-ers!
>>>>
>>>>I've just uploaded a new version of 'sidefonts', the two sideways fonts I developed to simulate rotated text on a VFP report.
>>>>
>>>>Thanks to the help of Jean-Pierre Overbeek, I've figured out how to get spaces to not get stripped out by VFP during the reporting process.
>>>>
>>>>The new font package is still under download #
19300, but the new fonts are now in 'sidefonts-a.zip', instead of 'sidefonts.zip'. The link will be broken until the file is dropped into the 'download' area by the UT gods.
>>>>
>>>>Enjoy!
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison