Your It department is dead right
Are they worried about the actual vb runtime files, or third party controls. If it's the actual vb runtimes then exclude them from the distribution, get a list of em and verify with the sysop that these files exist on the servers/clients and that the versions are the same as the ones you are trying to distribute.
Then when you generate the vb distribution, take them out of the distribution list. Trial and error with a simple "Hello World" app should get you to the correct stage.
Have trialed Fusion....and my opinion is it is over priced. You get a download, no cd no manuals for approx $1000(AUD)...for that sort of money l expect a cd, at least one manual, and a demonstration app.
Will try Konan555 link and see what that does.
Your only other options are to move to Delphi, c++, or a similar langauge that generates stand alones.
Konan555 thanks for the link dude
Downloading the trial version now. At $143 odd oz dollars is certainly better value than Fusion.
Just to bring this old fella up
Couldn't the dll's just be put in the same directory as the executable?