In a Client/Server environment, files which contain lookup data (such as the state tax rate file in Appendix 2 of the Sesame Programming Guide) should optimally be stored on the Server.  This is for both security reasons (because you don't want end users to be able to edit the file) and deployment reasons (because you don't want to modify every client desktop when the tax rates change).  Sesame definitely has the ability to open Server side files, but @ServerFileDialog requires user intervention.  I would like the ability, using a command such as FileOpen, to open a file in the working directory of the Sesame server.  Can I do this?  If not, my workaround idea is to store a delimited dataset in a Global Value, which is a less elegant and less secure solution.

Hammer wrote on Dec 19^th, 2007 at 1:28am:

That imposes two burdens:

1) One has to hard-code the path/drive.  Since a lookup/config file can exist in a fixed location (preferably the working directory of the Server instance), one shouldn't be required to hard-code path/drive information into the application.

2) One then needs to manage the file system access rights of the lookup/config file such that only authorized users are able to write to it.  This headache would be avoided by hiding the file behind the wall erected by the Sesame server.