Dawn,
One thing I don't think you mentioned is the file structure. Tell me if I'm
wrong. The file structure is not like U2 at all. Unlike U2, and all other
PICK environments, which have separate files for each table, Cache has one
file that contains all of you tables. The one big problem with
Hi Jerry -- I started responding and decided I wasn't certain about
some points so I passed your question along. I will get back to you on
this when I get a response. What I do know is that the file structures
look the same to any application software, but different to the OS.
I can also pass
One thing to be careful with Cache is that it does not have the same
transaction processing as U2. With U2 modifications made in a transaction
block are not visible to other users until commit, as I have been advised in
Cache those modifications are immediately visible to other users.
Regards
I'm pretty sure you are right about that, David. We had them explain
transactions and it sounds like it makes complete sense to use that
feature in Cache' where I have never used it in U2. --dawn
Dawn M. Wolthuis
Tincat Group, Inc.
On 4/17/07, David Jordan [EMAIL PROTECTED] wrote:
One thing
