Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
One or more files in <merge module name> have different versions than those installed on this machine?
87 views
Skip to first unread message
Paul Coleman
Mar 10, 2001, 11:02:43 AM3/10/01
to
Hi,
First, is this the best place to post questions about VSI and VB?
I am getting the message "One or more files in <merge module name> have
different versions than those installed on this machine." for MSVBVM60.MSM,
MDAC.MSM and TABCTL32.MSM. I can find any explanation on how to resolve
this problem. There is no explanation about what it found or what it
expected to find. Any help would be appreciated.
Thanks,
Paul Coleman
First, is this the best place to post questions about VSI and VB?
I am getting the message "One or more files in <merge module name> have
different versions than those installed on this machine." for MSVBVM60.MSM,
MDAC.MSM and TABCTL32.MSM. I can find any explanation on how to resolve
this problem. There is no explanation about what it found or what it
expected to find. Any help would be appreciated.
Thanks,
Paul Coleman
Glen Conway
Mar 11, 2001, 8:18:47 AM3/11/01
to
I usually disable the message from the project properties dialog in
InterDev. Doesn't seem to cause a problem.
InterDev. Doesn't seem to cause a problem.
"Paul Coleman" <Paul.C...@CoSeCo.com> wrote in message
news:OSZSXuXqAHA.1992@tkmsftngp03...
Paul Coleman
Mar 12, 2001, 8:28:57 AM3/12/01
to
Hi,
I am trying to understand why the messages are there and how to resolve
them. I am not comfortable just ignoring them.
Thanks,
Paul Coleman
I am trying to understand why the messages are there and how to resolve
them. I am not comfortable just ignoring them.
Thanks,
Paul Coleman
--
Get your free web based eMail address at iUpTown.com ->
http://www.iUpTown.com/eMail
"Glen Conway" <glen....@fpcom.co.uk> wrote in message
news:OGHKT3iqAHA.1336@tkmsftngp02...
Glen Conway
Mar 13, 2001, 10:16:59 AM3/13/01
to
Fiar comment. I point VSI to look for merge modules in three places. The
first is \Program Files\Microsoft Visual
Studio\Common\Tools\VSInst\BuildRes, second is the location on our network
where merge modules for our software live and the third is the location of
the merge modules included in VS SP4. For an example we'll use MSVBVM60.DLL
contained in MSVBVM60.MSM. The version in the BuildRes folder is 6.0.88.77
and the version in the VS SP4 folder is also 6.0.88.77. The version however
in my windows system folder is 6.0.89.64 because I have installed VS SP 5.
first is \Program Files\Microsoft Visual
Studio\Common\Tools\VSInst\BuildRes, second is the location on our network
where merge modules for our software live and the third is the location of
the merge modules included in VS SP4. For an example we'll use MSVBVM60.DLL
contained in MSVBVM60.MSM. The version in the BuildRes folder is 6.0.88.77
and the version in the VS SP4 folder is also 6.0.88.77. The version however
in my windows system folder is 6.0.89.64 because I have installed VS SP 5.
Now if you apply that to all the DLLs in the MSMs you can see why I turn off
checking.
Thanks
Glen
"Paul Coleman" <Paul.C...@CoSeCo.com> wrote in message
news:ewbT7hvqAHA.1436@tkmsftngp03...
Paul Coleman
Mar 13, 2001, 3:25:26 PM3/13/01
to
If you have VS SP5 installed, why isn't the SP5 merge modules used instead
of the SP4 ones? Did you have to make the merge module pointers manually or
are they automatically added when an SP is installed? If manual, where are
these changes made?
Paul Coleman
of the SP4 ones? Did you have to make the merge module pointers manually or
are they automatically added when an SP is installed? If manual, where are
these changes made?
Paul Coleman
--
Get your free web based eMail address at iUpTown.com ->
http://www.iUpTown.com/eMail
"Glen Conway" <glen....@fpcom.co.uk> wrote in message
news:#hhDoC9qAHA.684@tkmsftngp03...
Glen Conway
Mar 19, 2001, 6:50:27 AM3/19/01
to
Because I didn't download them with SP 5 - only just put them on today ;)
"Paul Coleman" <Paul.C...@CoSeCo.com> wrote in message
news:#LzFev$qAHA.684@tkmsftngp03...
0 new messages