Why did your change require you to set the /force option?
If the linker is not complaining why set it? This is really just a workaround for problems that ( may) exist with the linking of your program.
Have you set the compiler warning level to 4? If you are getting warnings can you explain or remove them.
Have you produced a linker output file using /MAP option?
http://msdn.microsoft.com/en-us/library/k7xkk3e2(v=vs.80).aspx[
^]
If you produce the map file for both conditions (with and without changes) and compare them you will be able to determine what has been linked differently.
Other than that there is no simple answer to your question.
This is because what the /force option does is completely determined by your code and whatever symbols are unresolved or multiply defined.
16-03-2012 You have added this information to your question.
Member 3782238 wrote:
I am using the /force option due to the following Microsoft Article.. http://support.microsoft.com/kb/245434/pt-b[
title="New Window" href="http://support.microsoft.com/kb/245434/pt-b" target="_blank">^]
The answer as to why the exe is different in size has nothing to do with /FORCE. It is because this solution requires static linking of the MFC library. You were probably dynamically linking before. With static linking the MFC library is added to your executable. Static linking vs dynamic linking will always produce different size executables.
My earlier answer is still valid.