>Hello,
>
>I assume that is not reccommended, but has anyone seen any issues with running a vfp6 SP5 EXE application on a SP3 runtime DLL?

I was afraid weird things would begin happening, but I had troubles with the setup created with Install Shield Express (about that later) and simply had to allow several users to run sp5 executables on sp3 runtimes. Nothing weird happened, but then we're not using any of the advanced stuff - at least none of the stuff which was addressed in SP4 and SP5, so I figure we haven't hit any of the differences.

The trouble I mentioned was with comctl32.dll, which actually gets installed after a reboot - it's in heavy use while Windows is running, so it can't be replaced during the setup. It's one of the RunOnce things. The trouble is that practically each user had a couple of machines where this file was incompatible with something. I started checking versions and dependencies and found that there were two versions of this file lying around, with exactly same version numbers (all four parts of it), but different sizes and dates. The newer and larger one, though, had the update date older than its create date, and also older than both dates on the other one. The solution was to shut down the affected (infected?) machine, boot into DOS (or just command prompt level, on 9x machines) and manually replace this .dll with a version from any other machine with the same OS, which was probably quite hard to achieve on NT, but the users' IT folks made it somehow.

Eventually I've found the version which should work - its dates are newer, it's also few kilos larger, and guess what: it has the exactly same version number as the other two. This one comes with W2K SP2. Go figure.