Quote:Ray:
Thanks for the info.
Do you not see this as a problem ? For example, once I complete our clients application, various ones will need to run Xlookups on this important app on a regular basis. Is this not a risk to have it open all the time ? Is it still able to compact and repair properly ?
Sesame does not leave files "open". It only opens files while loading and while writing. Because writing is typically very brief, that leaves only a very small susceptability to "write failure" - those cases where an open file is left incomplete due to sudden OS or hardware failure. An open file is (in Windows) left, to some degree, "cached" in RAM. There may be a lengthy period between a write operation and the "flushing" of the cache - if a file is left open. Sesame keeps all of its files closed except while in direct operation on them.
Sesame "compacts" and repairs when the file is loaded, not during operation. That is why your files grow, rather than shrink when you delete records - until the next time you load the file.
Quote:Also, will XLookup work when the external database is on a different server session ? I haven't tried this yet.
Louis
Yes. But there is an issue that has been addressed in 1.1.3 (soon to be released). You can have two servers. Call them serverA and serverB. If the application "Customers" is loaded on serverA and a client on serverB does an XLookup on that application - it will load on serverB as well as serverA. In that XLookup is a "read only" type operation, that is okay. But because it is now loaded on serverB, a client also on serverB could then open "Customers" and run it without regard for the lock established by serverA. This is problematic. But, as I said, it is resolved in the next release.