Thank you very much for your help. I do not find the 'recordSet'
object Jeff mentioned. It seems that a lot of the growth in
experience with these objects is just getting familiar with what they
are, what they are named, where they are found, etc.
Dave
At 10:04 AM 2/28/2012, you wrote:
Well, as Jeff already pointed out, you could use either a
multi-dimentional array, or a dictionary. The dictionary approach,
is a quite simple one, first you get hold of the structure, and get
used to work with it. One benefit is, that the dictionary does not
have any preset limit. It simply grows bigger, every time you add on
a new entry. It also gives you quick ways of deleting entries. The
array approach, might be a bit easier if you know exactly amount of
entries, and if you want to do things like sorting, or directly
referencing an entry, based on its indixing number. It all will
depend on what you exactly is trying to perform, and the amount of
flexibility your array or dictionary should have.
There is few benefits with storing things on a file. OK, if you want
to have things backed up, even if a power failure should occur, a
file storing of your data might be in its place. Or, if you for
instance wanted to have the same data loaded next time your app is
being run - like if you had built a wordbook of some kind. If your
data will be random, or you need the app start with all fresh data,
a file might only slow down your app. This because the data has to
be written to, and read from, the hard disk all the time. With an
array, or a dictionary defined, your data will stick in the memory;
with all that means for speedy access. OK, in cases where your array
size would be extremely excessive, and the user would happen to be
rather cramped for memory, your app could fail due to the array
growing out of memory space available. In normal settings, on a
modern computer, this might not be much for an issue though. An
array of 8500 entries, holding 16bit numbers (meaning numbers up in
the billion range), you would be looking at a memory consumption of
something just under 20kb. That is 0.02mb, or even 0.00002GB; as you
can see, nothing to worry about on a modern computer.
When comes to the file system object, this is not a Window-Eyes
object, and likely not being dealt with in the WE app developers
manual, or the GWToolkit documentation. You might be better off,
doing a search on the net, for something like:
VBScript File System Object.
You also can try go to the below website, and follow the link for
the FileSystem Object, and it's sublinks. There you will find more
documentation on how to operate the object, and some nice sample codes.
http://www.piclist.com/techref/language/asp/vbs/vbscript/keyword.htm
----- Original Message ----- From: "David Helkenn" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, February 28, 2012 4:55 PM
Subject: Very Large Array Storage
Hello,
I want to write an app that will require a fairly large database
organized in arrays. There are around 8500 integer elements to be
stored in some 35 arrays. I thought I could have a static array of
the 35 dynamic arrays containing the integers. However, I do not
know how to get all that data initialized prior to the invokation
of the rest of the app. How do I get that data known to the app?
The behavior from a very high view, is the user presses the
activation hotkey, the controls are displayed in the dialog and the
database is available for use. I do not know how long it will take
to create the database, but it is subject to an easily implemented algorithm.
I am hoping to have this app as global. Will I need to use a file?
If so, where is the documentation related to the file system? I
find only a file/dir related document but there is no FSO in the GW
toolkit. Help please.
Using Windows7pro64 and WE 7.5.3.
Thanks...
Dave
