RE: dialog database engine failure

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi =?Utf-8?B?a2V0Y2g=?=,

Any takers on this unique situation? My user is starting to nip at me :)

The only other thing I can suggest is to open a Support Incident with
Microsoft support.

If you're open to more extreme measures, you could try creating a new
Windows profile for this user. If that doesn't help, try reformatting the
disk and reinstalling the machine from scratch.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)

.

Relevant Pages

  • Re: Revisions, track changes:
    ... I think I read somewhere that this may be causing a memory leak. ... worthwhile to open a support incident with Microsoft. ... This reply is posted in the Newsgroup; please post any follow question or reply ...
    (microsoft.public.word.vba.general)
  • RE: Remote Assistance problem
    ... I posted the question to the newsgroup you suggested on 4/30, ... I may have to open a support incident. ... > happy to open up a support call using one of your incidents.. ... > MsdnManagedNewsgroup Feedback alias and we will be more than happy to see ...
    (microsoft.public.platformsdk.security)
  • Re: VS.NET burps. Nobody else has seen this??????
    ... You should call Microsoft Support and get them to open a support incident ... > In short, while I am coding in the codebehind of a aspx page, color coding ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Programs Run Slower After You Install Windows XP SP-1
    ... As the KB article states, contact Microsoft Support. ... for the support incident if the fix applies to your system. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: MSMQ trigger app causes exception
    ... I recommend that you open a Support Incident with Microsoft Support. ... is not a known issue and not something that we can troubleshoot via news ...
    (microsoft.public.dotnet.general)