I currently have code portioned off into 12 SBAS files.  Each time I update or create a new one I have to distribute them to a dozen client directories.  I'm thinking of localizing them on the server and hard-coding the path to each file in my main code.  How will this change affect compilation time?

Thanks in advance.

This is an interesting idea, the batch file.  When would such a file be run?

I actually don't go to each machine, now.  I have each user's C:\Sesame drive mapped on my own workstation, and just do file copies across the network.  The only problem is when one of their machines isn't turned on at the time I'm working on it.  I have to keep a note to check back later when they're in and it's turned on.  It's not really too much of a big deal, but I thought if the compilation time was negligible I might localize the files.

Thanks Ben!  I experimented with a Sesame startup batch file that runs on the user machine, copies the files and then fires up Sesame.  Runs pretty quick, barely noticeable.  Only problem is that the command window stays open.  Microsoft decided a while back to eliminate "close on exit" from its shortcut properties switches, thanks Microsoft, that was stupid.  Rassafrassa....

By the way, a note to whomever edits the programming manual:  you need to include information on page 85 about the #include command that informs the reader he can hard-code paths to the sbas file.  The current example gives no indication this is possible.  Unless it's hidden elsewhere in the book, I dunno.  Page 85 is the only page listed in the Index that mentions #include.

Thanks again!