<div class="content"><p>The CreateFileScreen method creates a <a href="2356ea87-e273-444a-81e7-dac2a7dcd804" data-linktype="relative-path">Non-Persisted File Screen
Instance (section 3.2.1.3.1.2)</a> on the specified path.</p><dl>
<dd>
<div><pre> [id(FSRM_DISPID_FILESCREEN_MANAGER | 0x01)] HRESULT CreateFileScreen(
   [in] BSTR path,
   [out, retval] IFsrmFileScreen** fileScreen
 );
</pre></div>
</dd></dl><p><b>path: </b>Contains the path of the local directory
to put the <a href="809180e0-571e-40a0-8067-ffe89cbdcc40#gt_4029e82b-3938-41a4-9a52-dff21ec37dcb" data-linktype="relative-path">file screen</a>
on. </p><p><b>fileScreen: </b>Pointer to an <b>IFsrmFileScreen</b>
interface pointer (section <a href="ad685a32-0761-44ed-b10c-0c26de4934f0" data-linktype="relative-path">3.2.4.2.27</a>)
that upon completion contains a pointer to the newly created file screen. To
have the file screen added to the server&#39;s <b>List of Persisted File Screens</b>
(section <a href="6226bc6a-8346-416f-83f9-3c121bdd6e59" data-linktype="relative-path">3.2.1.3</a>), the
caller MUST call <a href="4c8f4ba6-bc57-43f5-ac0b-ddfda0b36982" data-linktype="relative-path">Commit (section 3.2.4.2.27.1)</a>.
The caller MUST release the file screen when it is done with it.</p><p><b>Return Values: </b>The method MUST return zero on
success, or a nonzero error code on failure.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>0x80045304</p>
  <p>FSRM_E_PATH_NOT_FOUND</p>
  </td>
  <td>
  <p>The specified path could not be found.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x80045306</p>
  <p>FSRM_E_INVALID_PATH</p>
  </td>
  <td>
  <p>The content of the <i>path</i> parameter exceeds the
  maximum length of 260 characters.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x80070057</p>
  <p>E_INVALIDARG</p>
  </td>
  <td>
  <p>The <i>fileScreen</i> parameter is NULL.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p>Upon receiving this message, the server MUST validate
parameters:</p><ul><li><p><span><span> 
</span></span>Verify that <i>fileScreen</i> is not NULL.</p>
</li></ul><p>If any validation fails, the server MUST terminate
processing and return a nonzero error code.</p><p>Upon successful validation of parameters, the server MUST
perform the following actions.</p><ul><li><p><span><span> 
</span></span>Create a Non-Persisted File Screen Instance with the <b>File
Screen.Folder path</b> property set to the specified path.</p>
<ul><li><p><span><span>  </span></span>Set
<b>FSRM Base Object.Id</b> to a <a href="809180e0-571e-40a0-8067-ffe89cbdcc40#gt_f49694cc-c350-462d-ab8e-816f0103c6c1" data-linktype="relative-path">GUID</a>.</p>
</li><li><p><span><span>  </span></span>Set
<b>Blocked file groups</b> to an empty list.</p>
</li><li><p><span><span>  </span></span>Set
<b>Notifications</b> to an empty list.</p>
</li><li><p><span><span>  </span></span>Set
<b>File screen mode</b> to <i>Hard screen</i>.</p>
</li><li><p><span><span>  </span></span>Set
<b>Template id</b> to an empty string.</p>
</li></ul></li><li><p><span><span> 
</span></span>Set <i>fileScreen</i> to the <b>IFsrmFileScreen</b> interface
pointer of the newly created Non-Persisted File Screen Instance.</p>
</li></ul><p>The new Non-Persisted File Screen Instance MUST NOT be
associated with an existing <a href="73d37c2e-5d40-4074-96dd-39cf217cdb52" data-linktype="relative-path">Persisted
File Screen (section 3.2.1.3.1.1)</a>.</p></div>