CompuServe Messages

Dennis, That sounds like a good idea to me. However, I'm not nearly competent enough around external function calls to create what you're describing. What I'd like to see someone do…and I'd pay for it…would be a generic installation program. It could read a file containing the filenames to copy or unzip from the source, then take care of the rest of the installation. If I knew enough about this stuff, I'd write a program like that in a flash, just so I'd have it on hand for future apps. For now, though, lacking something like that, I'll just continue to give my usual installation instructions to the user, trusting that far more than my own feeble efforts. I'm still trying as much as possible to stay within the VB internal stuff…for a couple of reasons. First, the more external calls a program makes, the more likely it's going to have incompatibilities with Win 3.1, I would think. For a shareware author, that's an unmitigated disaster, since everyone would have to be sent an update if the current version wasn't compatible. Since I charge just $15 for my shareware, I simply couldn't do that for hundreds of registered users without bankrupting myself. I'm assuming that MS is going to keep VB compatible with itself at least. So I remain a conservative, using only those calls, such as to the GDI's StretchBlt, which are unlikely to change. Ah well…. There are 3 Replies.