>>We have an app that runs continuously. Every few minutes, the interval is
>>user set on the form, we do an adir() and compare the array to a table. If
>>the table has a row (file name, time, size etc) which references a file
>>that has not been transfered we copy it to another directory and erase the
>>copy in the current directory. This app allows users to upload files to a
>>BBS system and we then capture the files for import to a database. We use
>>the table to track which files have been imported and make sure that we
>>only import a file once. This is a long winded explanation, but we have
>>had the app run for several months without running out of memory or
>>restarting. hth bob
>
>We've had something similar, a pharmacy warehouse where drugstores were
>supposed to be sending orders via modem, and get them filled in by the
>program (approved, partially approved or dismissed). There was an upload
>and download directory, and the files were coded by having a pharmacy's
>code in the filename (thus the ownership and recognition of which file a
>drugstore may download). For modem handling, renaming sent files etc we
>used one bugus 286 with no disk, running Telix. Now in the Fox part we
>didn't have timers available in 2.6 (and better we didn't), so I've
>written a download directory scanning routine and hooked it to the menu
>system - whenever a menu option was entered/exited, it triggered (well,
>not for all users, only for the ones who had to handle orders). The
>trick was that all the downloaded files to be worked on were renamed
>first, which is practically instantaneous, and then opened and
>processed; we've never encountered a conflict of two instances of the
>app trying to work on the same file.
>
>I guess it's the timers who are leaking memory, but it's just a guess.
>Your form had no timers?
Actually we did have timers which ran our entire app every few minutes to get the uploaded files
which were also renamed. b