Hi Doru,

Three people I am aware of have now reported issues involving this merge module - Francisco Caselli in message #972989, Chris Bohling in message #973890, and yourself. As Chris pointed out, the problem appears to be in the MSXML3 SP5 merge module, which evidently is not available for download. I don't know if VFP 9.0 deployments require MSXML3 SP5 or not, but if not then maybe it's okay to use the MSXML3 SP4 merge module until the problem with SP5 is identified and fixed. The SP4 merge modules are available for download from http://www.microsoft.com/downloads/details.aspx?FamilyID=c0f86022-2d4c-4162-8fb8-66bfc12f32b0&DisplayLang=en. AFAIK there has been no word from Microsoft on this, so it looks like we are left to make our own decisions here for the time being.

-Rick



>Hi Rick,
>Thanks for the link - I read it, and I understand that there is a bug in MSXML 3 modules, but I'm not sure what the conclusion is. Is it that we cannot distribute support for cursortoxml with VFP9?
>
>>See message#973890
>>
>>>We are trying to install VFP9 from a MSI built using Visual Studio .NET.
>>>First, we added all MSM files found in the 'Merge Modules' directory of the setup image. That did not work - running the MSI directly seem to work, it went trough trough the setup screens but it did not install the DLLs. Running it trough the server policies it logged the error 2613, saying that there is something wrong with the package.
>>>Next, we took a step by step approach:
>>>- added onle the vfp9runtime.msm - that worked.
>>>- added vfpoledb.msm - still ok
>>>- added vfp9rptapps.msm - still ok.
>>>- added XML support modules - this doesn't work (with the symptoms described in the beginning)
>>>I assumed that everything in the 'Merge Modules' directory is distributable - is that correct?
>>>Is there a known problem with the XML modules, and a workaround it?
>>>TIA