Quote:I specified "Start In: G:\Sesame\" so the users dont have to browse to find the Database App.
Use a rootdirs file on the server to start your users in the right directories on the server - no browsing necessary. By setting the "Start In" directory to a network mapped harddrive you are making the net generate twice the necessary traffic.
Quote:NTServer icon (used to launch sesame server) reads:
"Start In: C:\Sesame\"
That's fine.
Quote:The Application Settings path to pictures typically reads C:\Photos when NTServer is serving Sesame (Very Slow), but I have to change this to G:\Photos if running the server on a local users machine (Much faster)
Of course, this is because //NTServer/C: = //Steve/G:
When running client/server on two diffferent machines, Sesame has to pass the actual data of the image through the network from the server to the client. Set the rootdirs.ini file and the image path to be relative to the server - not the clients. If either is relative to the client machine, then your data is going through Sesame networking and Windows networking - slowing both down.
Quote:I considered making a new partition on //NTServer/C: called G: so I dont have to change the App Settings but I dont think this help with the speed issue.
Depends on setup.
Quote:Thanks for the FAST response, by the way! (As usual)
Steve in Texas
You are welcome. In general, remember that almost all file access is relative to the server, not the client. The only files accessed on the client's harddrives are programming saved/read in ASCII from the programming editor and saved HTML files when doing a Print Form to HTML export. These are notable in that they use a different file dialog.
Pages: 1
Need help with Server setup (Read 783 times)
