Paul,
It is RB2 that will grow, unless you use PACK TABLE, and potentially, SET RECYCLE ON. That said, you *could*, before DISConnecting, do: OUTPUT filename UNLOAD DATA FOR tablename OUTPUT SCREEN SET VAR varname VARCHAR = ['filename'] Now you have the contents of your table in a variable. Reconnect, create the temp table, write the varchar to a file and run it. Your data is back. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Paul InterlockInfo Sent: Monday, September 21, 2009 5:12 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Temp Table and RFF I was always under the impression that adding/deleting or dropping rows will over time will make the .R#1-4 grow. And I am looking at files verses rows. I may have deleted this email prior to sending (?), but awhile back I told somebody I use older laptops. They have really small drives. Not only Am I careful about db errors but I need to keep a low disk space. I will not even tell about the amount of FTP that goes on to make sure if these systems die I have the data prior to self destruction. Sincerely, Paul Dewey I thank you for the suggestion. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, September 21, 2009 4:55 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Temp Table and RFF Paul: Can you use a permanent table instead? Create one column in the table that will uniquely identify that workstation (CVAL('COMPUTER')). Have your program check at the beginning whether there are any rows in the table for that computer. If there are, either delete them or give a message to the user saying that there's already rows in the table, and what do you want to do? Then load your data, process it, and delete rows where column = (cval('computer')) at the end! Karen 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.
