Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Not enough storage is available to complete this operati
Message
 
 
À
29/10/2004 03:50:58
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Versions des environnements
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
00955580
Message ID:
00955832
Vues:
18
>>Hi everybody,
>>
>>I opened Object Browser and then typed in Command Window
>>oWord = createobject ('Word.application') and received an error: "OLE error code 0x8007000e: Not enough storage is available to complete this operation."
>>
>>So, now I have several questions:
>>
>>1) Why I receive this error and how can I fix it?
>>
>>2) Are there any improvements in Error dialogs in VFP9? E.g. right now I even can not copy error content in the clipboard. Does VFP9 have this ability?
>>
>>3) The Help was not helpful as well: < font color=blue>
>>Visual FoxPro
>>
>>OLE error code 0x"name" (Error 1426)You have received an error code from OLE (in hex), and a brief description of the error. The remedy depends on the error returned by OLE.
>>
>>So I wanted to send an e-mail about this topic. I clicked on Send feedback to MS and received another error message saying that IE default e-mail client is not properly installed. Well, IE is not my default Web Browser, but it has Outlook set for e-Mail (Tools\Internet Options\Programs. So, how can I fix this problem as well?
>>
>>Have an error trying to report a problem with an error :)
>__________________________________________________________________
>hi Nadya,
>
>I'll have a go at (1)
>
>Releasing oWord does not release the windword.exe process from memory.
>If you test long enough there may be a load of winword.exe processes in memory. You can verify with task manager, processes and sort on image name (descending)
>
>Solution.
>
>While testing make the Word app visible
>
>oWord.Visible = .t.
>
>
>Always quit word prior to releasing the object reference (with Release or going out of scope)
>
>#define wdDoNotSaveChanges         0
>		
>WordObj.Quit(wdDoNotSaveChanges)
>		
>#undefine wdDoNotSaveChanges
>
Hi Gregory,

At the time I tried this command in the command window I had Word already opened. Do you think, it was the problem? But I just tried again with the same error. What can I do to remedy it?
If it's not broken, fix it until it is.


My Blog
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform