Some more info and another questions: Some from the list have suggested storing the map data locally, and using the remote server for processing only. This may me the way to go, but if so we loose some of the benifits of using thin clients - mainly that we would still have to maintain a local server at each office. We've fiddled with network settings, and see that the thin client now out performs (in timed tests of common functions) both running MI off a PII300 64 MB RAM with data locally on that machine, and running MI of the same PC with data on our file server. However, it failed one test - we have a test mb app that draws 5000 points to the screen and times it. On one thin client it runs faster than a PC. Run it on two thin clients at the same time and it runs much slower. Now the question: Is this a processor thing? We've got dual PIIIs with much RAM in the test server, and we can boost to quad processors and up the RAM if needed BUT - can MI make use of additional processors? There was some discussion on the list a while back about this - looks like it cannot. Can anyone clarify how MI uses (or does not use) multiple processors? I'm especially interested in the most current version of MI (5.5 or beta 6?). I'll let all know what I find as we continue our testing. John ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
