Thank you both for your responses. Yes, we could use a cloud-based storage system for the Sailwave files, and I note the advantage of version control and shared usage that would offer. But that would require our team of scorers to all have access to the same cloud system, which might prove problematic. I personally have Dropbox, OneDrive, Google and Box accounts, but I doubt we could find one storage system with which all of our scorers are comfortable.
For 12+ years, we’ve been saving our Sailwave (.blw) files on our server, using the same filename as the .htm file, using a password-protected upload utility that doesn’t even require the scorer to use FTP. For example, results from our interclub long distance races (“long” being a relative term) are posted at https://nsc.ca/nsc_racing/results/2020/longdist/longdist.htm; the corresponding .blw file is at nsc.ca/nsc_racing/results/2020/longdist/longdist.blw, where anyone could access it if they so chose. (As a new user, I was limited to 2 links in a post.)
If you were willing to pursue this feature, yes, I agree, it would be good to automate saving of the file, prior to publishing. Until Sailwave offers the option to upload the .blw file, I think we’ll likely stick with our time-proven method, though it’s a little more clunky than the integrated FTP option.
BTW, while I am a newly registered forum user, we have been using Sailwave at our club since 2007, and contributing periodically to your great product. Results dating back 20+ years (pre Sailwave) are available at Results for NSC & Interclub Racing | Nepean Sailing Club. Unfortunately, all recreational boating here is currently subject to a government ban, but we are hoping to get out sailing very soon.