# Run Finalbuilder script from network(only read access)

**URL:** https://www.finalbuilder.com/forums/t/run-finalbuilder-script-from-network-only-read-access/2233
**Category:** Discussion
**Created:** [December 11, 2013, 2:26am UTC](https://www.finalbuilder.com/forums/t/run-finalbuilder-script-from-network-only-read-access/2233 "2013-12-11T02:26:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![adityabhat](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/adityabhat/32/147_2.png) [@adityabhat](https://www.finalbuilder.com/forums/u/adityabhat)
#### Post date: [December 11, 2013, 2:26am UTC](https://www.finalbuilder.com/forums/t/run-finalbuilder-script-from-network-only-read-access/2233/1 "2013-12-11T02:26:24Z")

</div>

Say there is a finalbuilder script in the network share server&nbsp;(read access only), if that code is to be executed, as soon as I try to open the fbp7 code, there is a message saying access denied. Although I have read access, this error appears. I think, this error is because, on opening the finalbuilder script, it tries to create .fbl7 and .fbpInf files. Is there a workaround to avoid this problem( without giving write access to the user), or is there a way to create these files in some other location?

---

<div class="post-metadata">

### Author: ![nevar](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/n/c4cdca/32.png) [@nevar](https://www.finalbuilder.com/forums/u/nevar)
#### Post date: [December 11, 2013, 10:49am UTC](https://www.finalbuilder.com/forums/t/run-finalbuilder-script-from-network-only-read-access/2233/2 "2013-12-11T10:49:32Z")

</div>

Hi Aditya Bhat,   
  
 As it turns out there is no way currently to turn off this behaviour or redirect it under the FinalBuilder IDE. With the command line runner the log can be redirected with the /L param. Yet there isn’t a way currently to redirect the location of the fbpInf file.   
  
 As it stands there are a few files which are generated / used in the same directory as the script. A potential work around for the moment would be to copy project to a temporary location, run it, then remove it. A decision would have to be made as to what to do with the other files which are corrected. Most importantly the project info file (fbpInf) which holds persistent project variables, and the project log file (fbl7).