Not sure if there is a problem with this in windows or not, but I ran into this problem in a run time solution this morning. I was running some reports for records that have a container field in them, I printed the report about 40 times with different non overlapping record sets then I started having no record found errors when running my printing script which just goes to a different layout in preview mode and then prints. I noticed a slowdown after about the 20th record set but didn't think much of it. I had to restart the runtime solution to get it to clear out.

Besides checking for error 101 (record missiong) unless I should check for some other error, how might I get filemaker to flush it's memory cache?

I'm also unsure this occurs with an unbound solution or not, I need to do more testing to see that I can get it to hang up in the run-time solution one more time, then i'm going to try to get it to do this in a non run-time file.

did u use a "Perform Find" somewhere in the script? there is a problem with that which i encountered earlier... it is a little hard to explain the problem, but u can take a look at this thread to get a little understanding... dunno if it's the same problem that we are talking about though.

http://www.fmforums.com/threads/showflat.php?Cat=0&Number=123304&an=0&page=2#123304

nope, not doing a perform find in my script steps. The script assumes the current found set is what should be printed so it simply goes to the report layout, toggles to preview mode, then pauses, and if yes is clicked, it'll start doing the print statments.

the records do not get lost in the database, just in the found set. for any report in the one file of this multifile solution. reports from other files are fine.

it does not always reset itself when closing the file, or printing a report from another related record.

the foundset is generated from a go to related record call from a related file, how ever if i redo the find, the report does not seem to reset it's found set pointer

I wonder why the run time solution will loose track of the found set until a print or toggleing of a preview mode in a different file will recover the link to the found set.

for now i'm done testing in a run time solution, Going to see if i can get it to reproduce the same things inside filemaker developer itself

argh, my bad, this seems to be a case of the preview screen not updating properly. cause i guess the report prints as it should...