Can an MFC application use in-memory temp files for embedded OLE objects?

Consider an application such as Wordpad which uses a CRichEditView.

Presume a new SDI application is created in Developer Studio using the wizard based

on CRichEditView.

In explorer, it is possible to right click a .jpg file, and select "copy", and then

paste into the new SDI application. If "elephant.jpg" is pasted, then a rectangle

will appear in the rich edit view entitled "elephant.jpg". If that rectangle is

double clicked, then the default .jpg viewer is started, displaying the elephant.jpg

picture.

When the embedded object (elephan.jpg) is double clicked, a temporary file is

created, and the object data (which is embedded in the rich text) is written to this

temporary file. The default application associated with the .jpg extension is

started and passed the name of the temporary file.

I wish to avoid having a temporary file written to the hard drive. Does windows

support the concept of in-memory files? I mean, in a manner that allows an

application to open a file for reading (presuming it has the filename) and be

unaware that the file is actually in-memory. The format of the pathname could

indicate to Windows that the file is in-memory, rather than on a persistant storage

medium.

If Windos supports such in-memory files, is it possible to specify that the

temporary file created when a .jpg embedded object is opened in a CRichEditView be

in-memory?

Is there some way to avoid having a temporary file written to the hard drive when

the embedded object is opened?

Thanks