Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Not enough storage is available to complete this operati
Message
From
29/10/2004 03:50:58
 
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00955580
Message ID:
00955699
Views:
20
>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
Gregory
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform