Leemi
Wed Aug 11 08:42:10 CDT 2004
Hi John:
Since the error seems to be with a Word or Office file, I would post this
error information to a Word or Office newsgroup. They will probably be
more familiar with mso9.dll and any updates that might be available for
this file.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here:
http://msdn.microsoft.com/vfoxpro/
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
Further to my earlier post on this topic (below)
The client has no antivirus software loaded - but does a scan from 'trent
microsystems' (internet site that scans your system) each week
However I was able to find several references to this application error in
the application event log:-
Faulting application winword.exe, version 9.0.0.3822, faulting module
mso9.dll, version 9.0.0.3821, fault address 0x00081c2a.
But cannot find any help on the knowledgebase that would fit the clients
situation
Where can I find out more about this error?
Thanks,
John
****************************************************************************
***********************
Hi John:
Have you disabled any your anti virus software? Do you get the error if
you boot in Safe Mode.
Have you used event viewer in XP to look at the Application event log to
see if you can get any additional information about the memory exception?
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here:
http://msdn.microsoft.com/vfoxpro/
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>Hi John,
>Further to my earlier post on this topic (below)
>The client has no antivirus software loaded - but does a scan from 'trent
>microsystems' (internet site that scans your system) each week
>However I was able to find several references to this application error in
>the application event log:-
>Faulting application winword.exe, version 9.0.0.3822, faulting module
>mso9.dll, version 9.0.0.3821, fault address 0x00081c2a.
>But cannot find any help on the knowledgebase that would fit the clients
>situation
>Where can I find out more about this error?
>Thanks,
>John
****************************************************************************
***********************
Hi John:
Have you disabled any your anti virus software? Do you get the error if
you boot in Safe Mode.
Have you used event viewer in XP to look at the Application event log to
see if you can get any additional information about the memory exception?
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here:
http://msdn.microsoft.com/vfoxpro/
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>Hi John,
>I think the 1st thing to look for is access rights. Does the user have
>sufficient rights to open & edit the document?
>Is the document on a network share?
>The structure for win XP against W2k isn't all that different (from
>developers POV). The Office version is the same, so that shouldn't be the
>cause of the problem.
>IF VFP is installed on the machine, you can even start it up and figure out
>which operation actually generates the fatal exception.
>HTH,
>Sietse Wijnker
>"John Davy" <spamblock_john@multiarray.com> wrote in message
>news:%23mVHAJucEHA.3988@tk2msftngp13.phx.gbl...
> I have a problem at one of my clients running my vfp6 app on xp home and
> calling winword8 (office 2000)
> They were win 2000 running with no problems - their tech just did an
> upgrade.
> The document is a mail merge document and I provide a button that allows
> them to view & edit the document (code snippet below)
> word opens and then crashes after about 5 seconds with fatal error message
> If I try again - winword doesn't even open & I get the fatal error message
> followed by a vfp error 1426
>
> I can close my application & open the documents in word with no problems
>
> Where should I start to look for a solution to this problem
>
>
>
> **************
> if file(cDocument)
> oW = createobject("word.application")
> oDoc = oW.documents.open(cDocument)
> else
> return
> endif
>
> if type("oDoc") # 'O'
> ow.quit(.f.)
> release oW
> return
> endif
>
> ow.visible = .t.
>
> ** wait for word to be closed by users
> do while type("ow.visible") = 'L'
> if isnull(ow)
> exit
> endif
> enddo
>
> release oDoc
> release oW
> ******
>I think the 1st thing to look for is access rights. Does the user have
>sufficient rights to open & edit the document?
>Is the document on a network share?
>The structure for win XP against W2k isn't all that different (from
>developers POV). The Office version is the same, so that shouldn't be the
>cause of the problem.
>IF VFP is installed on the machine, you can even start it up and figure out
>which operation actually generates the fatal exception.
>HTH,
>Sietse Wijnker
>"John Davy" <spamblock_john@multiarray.com> wrote in message
>news:%23mVHAJucEHA.3988@tk2msftngp13.phx.gbl...
> I have a problem at one of my clients running my vfp6 app on xp home and
> calling winword8 (office 2000)
> They were win 2000 running with no problems - their tech just did an
> upgrade.
> The document is a mail merge document and I provide a button that allows
> them to view & edit the document (code snippet below)
> word opens and then crashes after about 5 seconds with fatal error message
> If I try again - winword doesn't even open & I get the fatal error message
> followed by a vfp error 1426
>
> I can close my application & open the documents in word with no problems
>
> Where should I start to look for a solution to this problem
>
>
>
> **************
> if file(cDocument)
> oW = createobject("word.application")
> oDoc = oW.documents.open(cDocument)
> else
> return
> endif
>
> if type("oDoc") # 'O'
> ow.quit(.f.)
> release oW
> return
> endif
>
> ow.visible = .t.
>
> ** wait for word to be closed by users
> do while type("ow.visible") = 'L'
> if isnull(ow)
> exit
> endif
> enddo
>
> release oDoc
> release oW
> ******