To patch or not to patch?

[krilbe]

Hi,

Our product consists of a small VB 6 (Win32) program and an Access DB accessed via ADO+Jet engine. Every month a new DB is issued. On occasion the new monthly issue also contains a new version of the VB program. Our customers will not install every monthly issue.

I would like to publish a single installer on our website that will detect if our product is installed (in which case it will upgrade) or not (in which case it will make a fresh install).

Is this possible with:
- Express?
- Developer?
- Studio?

Have I got it right if I am under the impression that this would not be solved using patches, but normal install builds? I'd simply keep the same product code but change the revision code. Right? And a subsequent uninstall would remove "everything"? (Our program does not create any files on the target machine.)

It would be nice if the upgrade case would not ask for installation folder and shortcut folder, but simply update the files that are out of date. Is this possible with:
- Express?
- Developer?
- Studio?

Thanks,
Kjell Rilbe