Infinity wrote on Sep 3^rd, 2007 at 8:53pm:

I'll have Ray contact you and ask for what he thinks would be most useful.

Quote:

It usually happens when a mapped hard drive is in conflict with the server shortcut settings. The OS lies to Sesame and tells it that the database files needs to be sent through the net several times when they are already where they need to be.

Quote:

You can tell because things go slow, behave differently client/server as opposed to standalone and sometimes you get "Too many connections" errors when you don't think you should be. 

AARRGGHH!!  Drive mapping.  DRIVE MAPPING!

Sesame Server was set to "Start in" F:\Sesame\Miara.  This was done a while ago when I had problems getting my XLookups to work.  For a while they were hard-coded, and since all the workstations see the server as F:\...  (Turns out the problem was actually with the pre-index xlookup .ini setting, which was buggy at the time.)

But it was never changed back to C:\Sesame\Miara when that problem was solved.  The server sees itself as C:\ of course, so telling it to start in F:\ (a drive map I had created to try to fix the earlier problem) was, as Erika says, moving the whole app across a network.

This morning I changed the -server's icon to start in C:\Sesame\Miara, copied my "bad" app (with all 25219 workorders, filesize 118,802 KB) to the Miara directory...and the app opened happy as a clam.  A very happy clam.

Let me repeat myself...AARRGGHH!!

If I get a chance, I plan to go back in time to yesterday morning and inform myself of this.  But I'll wait until after payday, so as to be sure I get my holiday pay first.