I have a tab on a form that has lots of Check Box elements. Each check box represents a paper form that is a necessary part of a clients file. I have logic associated with the box that goes out to a directory using FileExists() and sees if the faxed document has been received and if it has it turns the box green, if not it turns box red to visually notify the user if the form is available.

This indicator is used in association with the user and a command button to @Asynchshell to a file viewer so a user can see the document when needed.

This form is used as a subform.

The logic below (for one box) is executed on form entry. It works as desired from the software point of view, however am I causing a problem for hardware by having it read the hard drive or network drive looking for 50 or 60 files every time a form is entered?

Also since this form is used as a subform I believe it thinks I am entering the form everytime the tab gets focus or loses focus.(the reason I believe this is because if I put a writeLn() statement in as commented out below it constantly activates)

Am I building a problem into my application. Is there a better way I should consider designing this feature?

I thought about only having it FileExists() if the element =1 however there still would be lots of activity and it would not deal with a file being removed.

All thoughts appreciated.

Thanks



// This checks to see if the PIO form is in the directory and puts a check mark in field element Ynpoi and turns box green or red for easy visual notification.

VAR VpoiYN as string



                 VpoiYN = ("c:\Images\poi\" + @str(propertyfirst+propertylast) + ".tif")
     


iF      FileExists(VpoiYN)
{
     YNpoi = 1
     @color(YNpoi,0,10)
     
}
else
{
     YNpoi = 0
     @color(YNpoi,0,12)
     // Writeln("cant find it")
}