Greetings,

we use a filefindfirst *.pay to start processing a file.
After processing the file is moved to a 'old' directorie.

In the processing something went wrong and the file was
renamed to *.pay_niet_verwerkt.

in the next run of the loop it started processing the file
*.pay_niet_verwerkt and after the same error as previously
it was renamed to *.pay_niet_verwerkt_niet_verwerkt.
This went on for some time causing the file to get a very long filename.

is this a known behaviour of filefindfirst?

never mind, a second filefindfirst at the end of the loop had the wrong format, causing the loop to repeat and repeat