PDW error when building setup package
Jerry West
error. Today though, the PDW returns the following error "Invalid procedure
call or argument". Nothing has changed about my project which is a simple
ActiveX control project. It does not use a database, Access or any other
files related to a database. I've searched around for others who have
experienced this error and they all seem related to Access databases which
I'm not using. Does the PDW create a log file anywhere I could review? I've
looked in the package folder but don't see one. Anyone else have this
error/know of a solution?
Thanks,
JW
Jim Carlock
: I've been building a setup package for my project for days now
Don't know much about PDW as I've run into problems with it in
the past myself. There's a couple other installers though, freely
available that don't run into those problems.
I've used InnoSetup (http://www.jrsoftware.org/) in the past and
it is an outstanding product.
There's also, NSIS (http://nsis.sourceforge.net/).
Both represent outstanding installers, but I can only vouch for
InnoSetup. I've seen commercial software developers employ
both of those products (Adobe, et al).
If you go with InnoSetup, it basically employs a Pascal syntax.
NSIS on the other hand tends to employ PUSH and POP (like
assembly language) for passing variables.
Also, if you decide to try InnoSetup, also get InnoScript...
http://www.randem.com/innoscript.html
It has a PDW converter to help you out. It might take a week
to get familiar with it and get your installer up and running 100%,
but you'll never go back to PDW once you've used these.
Jordan Russel, the maker of InnoSetup, also runs a news servers,
where you can find links to those through his website. He monitors
posts to his newsgroups and replies to them as well.
--
Jim Carlock
Post replies to the group.
Ralph
"Jerry West" <j...@comcast.net> wrote in message
news:12v3jkh...@news.supernews.com...
After the known bug with links in MSAccess/Office Apps, the other related
condition is a reference to a component, thru a layer of indirection, that
can't be resolved by P&D. WinDbg may help isolate the exact one. Attach it
to P&D.
Make sure P&D isn't complaining about any missing dependancies. If your
changes included any other modified components re-create the dep files.
Often this is only momentary confusion. Cleaning out the project files -
especially deleting any .OCAs often cures it. Or rebuild the Packaging
script.
-ralph
Jerry West
JW
"Ralph" <nt_cons...@yahoo.com> wrote in message
news:L7-dnbXtEa6igW_Y...@arkansas.net...
Jerry West
compatible yet but I think I'm going to give them a hard look.
JW
"Jim Carlock" <anonymous@localhost> wrote in message
news:unJqTHqY...@TK2MSFTNGP02.phx.gbl...
MikeD
> Yep, I've heard good things about InnoSetup. Not sure if they are Vista
> compatible yet but I think I'm going to give them a hard look.
"They"? Not sure what you mean by "they" (the 3rd-party tools perhaps?).
Well, dunno about the 3rd-party tools, but IS itself apparently is
compatible with Vista.
http://www.jrsoftware.org/files/is5-whatsnew.htm
BTW, a new version (5.1.11) was just released on 03-01-2007.
--
Mike
Microsoft MVP Visual Basic