Prevent A SUP Package from Overwriting a SUP Directory tree
At 3 customer sites, someone has mistakenly entered in an incorrect path for a SUP package and overwritten the package source for other packages. For example, it's common practice to use \\server\share\<year>\<month> for package source. If I Package A uses \\server\share\<year>\<month>, and then a Package B is created and uses \\server\share\<year> as the package source, the <month> folder is overwritten and Package Source A has been corrupted. Might it be possible to prompt for "Are you SURE - this will overwrite the source for these packages:..." in such a scenario?