On Saturday, June 28, 2003, at 12:10 AM, Mark Brownell wrote:
I want to put the XML text of each transaction into 300 separate items of an array. I then would like to save this array as an external file. It wouldn't be saved as text it would be saved as an array file. I could then use answer to open it with my application that could then access it.
You CAN do exactly that by using a "data stack" via custom properties! See this excellent post by Richard http://www.sonsothunder.com/devres/metacard/tips/stk001.htm
excerpts from that post:
"""
The main benefit of using a stack file as opposed to a text file is the hierarchical structure afforded with objects and their custom properties.
Remember that every Rev object can have custom properties, and even multiple sets of custom properties. Accessing these is very fast — much faster than fields, and only a tiny bit slower than globals. You can use array notation if you like, and they can store binary data as well as text.
Since a new stack file contains one card in one mainstack, you instantly get this rich structure for organizing your data (for just 363 bytes of overhead):
...
Because the storage space and access speed overhead are so low with custom properties, you can use stack files for data sets as large as memory allows and expect pretty snappy performance. In this sense, it rivals Panorama and other RAM-based databases, with all the ease and flexibility of an xTalk.
"""
and to emphasize Monte's message earlier
""" -- create and populate your array put whatever into tArray["something"] -- use the following to save the array set the customProperties["myArray"] of stack "savedArrays" to tArray save stack "savedArrays" -- use the following to load the array put the customProperties["myArray"] of stack "savedArrays" into tArray
"""
Alex Rice, Software Developer Architectural Research Consultants, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED]
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
