Randem Systems Support Board

Excellent.  Thanks.

dglienna,
 
Yes, if you have email processing enabled in NAV your email will go through NAV. And yes, as long as you do not remove and re-add the MAPI control again it will not appear in your VBP file.
 
As long as you have created the script without the offending file, you will be able to compile.

Do you think that the email that my program sends goes through NAV on the users machine (if they have it)?  Also, as long as I don't add the MAPI control again, I should be able to recompile (as the offending file is not in the VBP any more)

dglienna,
 
I believe that the only change to the script was the removal of that file which you do not need to distribute. So, When you re-create the script just remove that file. Then you will be able to recompile without error.

Current being the one that we just solved.  AFIK, the current one was the issue that prevented the program from running.  I just wondered what caused the error message during the install. I assume that it was the auto OS update, but I'll know for sure when the user installs it.
 
On an off note: By turning back on email protection, will I be able to compile without another error, or will I have to repeat the scenario?  I am going to be installing a resizer control which may require generating a new script, unless I can copy the reference by hand.  In the meantime, the old script should work for minor changes to the VB code, if any problems come up.

dglienna,
 
What is the current error you are refferring too?

That seems to have done it.  What's the story on MDAC 2.8? Does the software use the October update to MDAC?  I sent him a P&D verion that forced him to update files, then I used Inno and sent him a project to test that worked successfully, and installed MDAC 8.  When I sent him the new project, the installation failed at MDAC2.8.RTM being incompatible with previous versions of Windows. He clicked cancel and came to the current error.

Thanks. I will try that today.

dglienna,
 
The best way to handle this would be to remove the MAPI Reference, then disable the email handling portion of NAV. Then re-add the MAPI reference to your project. This will probably remove the NAV file in question.
 
After re-running InnoScript the file should not exist (or you could just remove the file from the script also). This should remedy this problem.

The client does have a newer version of NAV installed

There was a different version on the client computer. What do I need to do in order to deploy my app? I can't remove the reference in my vbp file, or the program won't run here. The program installed on a workstation with the same version of the file intalled already.
I don't understand why the reference was added in the first place.
I also don't want to require clients to have NAV

dglienna,
 
Also, if this error happens on your target pc. Does the target PC have another version of the AntiVirus Software installed. Perhaps a newer version?

dglienna,
 
Are you saying that the ScrBlock.dll file is the wrong version? If so do a search of your hard drive and see if you have other versions of this file.
 
Also be aware that since this is a Symantec AntiVirus file, it may not work without the AntiVirus software already installed on your target computer.

if i delete the reference, the program doesn't load the MAPI control, which is needed to send email. I'm using martys registration scheme to do a one-time send of email.
I want INNO to work installing this file.  It could go in the auto updater, but i would think inno would me smart enough to be able to install it.  
The program is failing due to wrong versions.

dglienna,
 
Make what work with the file? What are you doing that this file is creating a problem?