Does anyone know of a way to control the directory that the @LocalFileDialog command starts out in? It seems to default to the local directory of sesame itself -- which ordinarily wouldn't be a problem except that my users aren't particularly adept at navigating file structures.

What I'm trying to do is create a file management system. The binaries aren't being saved as part of the database. I'm using the best practice of saving the location of each file instead. It works, but it would be nice to start the dialog thrown up by @LocalFileDialog to start out on their 'desktop' location.

Anyone know of a way to do this, or a possible workaround?