Or at least a TStringList Object, which the TStrings are the basis of the
Listboxes, ListView, Comboxes and the like. You can muff an array by using
a hidden variable listbox and manipulate it and use the FileSave and
FileOpen methods if you need to preserve data outside the db.. Get in the
habit of mapping all your persistant data to your UserTemp folder.
----- Original Message -----
From: "Dennis McGrath" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, September 21, 2009 4:59 PM
Subject: [RBASE-L] - RE: Temp Table and RFF
I think this demonstrates the value of adding arrays to the arsenal of
variables available to the programmer. As long as you are connected to a
db, tables or temp tables make useful arrays. But they certainly are not
available when the db is disconnected. Variable arrays would fill the bill
nicely. In addition they would often be a better choice than temp tables,
even when connected.
My opinion, food for thought,
Dennis
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Paul
InterlockInfo
Sent: Monday, September 21, 2009 3:45 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: Temp Table and RFF
To explain in a little more detail.
I have users run a compiled rff. This form when it opens collects
information regarding files etc.... It then disconnects (it also stays with
a users menu open). And waits (for hours if somebody is going to use me).
Well in the start.epp of the rff I created a temp table- that table is going
to drop on disconnect. So why not just wait for the user to press something
and that triggers this that. That is assuming the user did not go and use a
program behind (MS-Explorer) then the files could create and I would have
missed this file. This is all for a proprietary program and monitoring the
files.
In this rff is also a timer eep. When it goes off the db is not connected
-table is deleted (it was a temp/table! so it did what temp does). And I
have to recreate it.
Now we know (?) temp tables do not increase the size of the db. But this
routine of opening a db and closing just to wait for the user to select a
function every 10 minutes. It could never happen all day or it could happen
every 8 minutes all day. It could take its toll on the db, gosh forbid a
electrical spike, interference of ???, ...... etc... open-create temp
table-drop-disconnect. I just like db stilling closed till need, users can
be cruel to db's.
RBase is working exactly as expected. But sometimes there is a process that
is available that is better. I have found so many useful tips on this list
I cannot begin to thank all of you. I review the old and new emails and in
this case I missed the one from Mike B. that would work. (I think, I need
to get it to work for me)
I wanted to follow up and better explain, but also the previous email was
sent quickly to make sure there were no misunderstandings. Not trying to
fill the email daemon server.
Sincerely,
Paul Dewey
I hope this helps Bob, my first response was short. But I also DO NOT type
fast! ;)
