I have a runtime solution with 2 files. The main file has a script that opens the second file, finds and deletes all records, and imports records from the main file. This script works great on machines running Win 95 and 98.

On the Win 2000 machines, the main file works fine, but freezes the machine every time this open/find/delete/import script is activated. Both files need to be recovered after rebooting. The same file transferred to a Win 9x machine works fine after the files are recovered.

We also tried to reinstall the runtime solution on a new Win 2000 machine, in case there were other software conflicts, but get the same result.

Is anyone aware of Win 2000 conflicts? If so, is there an upgrade or other fix?

Thanks

I have seen file corruption that is platform, or even OS version specific. Meaning that although the file is corrupted, different OSes behave differently, some of them not even appearing to be effected.

If you can reproduce the script in a new file from scratch, and reproduce the crash, then perhaps you found a bug. In that case it should be reported as soon as possible:

http://www.filemaker.com/company/product_problems.html

If you cannot, then I suspect the file is corrupted in such a way that either recover is missing it, or it is some reappearing condition perhaps caused by corruption in another file that was overlooked.

Thanks for the reply. I have an update, which may or may not help diagnose the problem more exactly.

The freezing and file corruption described in my first message happened on a machine running Win 2000 Service Pack (SP) 2.

When I tried an exact copy of the file on a Win 2K SP 1, the machine didn't freeze, but it did hang for about 30 seconds when going from File 1 to File 2, and back to File 1 again. Unlike the first instance, I didn't get a "damaged file" notice for either file.

Question 1: Does the info above give you any more clues?

quote:

---

If you cannot (reproduce the crash in a new file), then I suspect the file is corrupted in such a way that either recover is missing it,

---

Question 2: If the file is corrupted and recover isn't catching it, is there anything I can do besides starting completely over?? This is a very complex database!

quote:

---

or it is some reappearing condition perhaps caused by corruption in another file that was overlooked.

---

Question 3: By "another file," do you mean another -data- file included with this solution, the .dll files needed to run the solution, or a completely unrelated file (such as a software conflict with something else on my hard drive)?

Thanks much for your patience and expertise.

Mary Z

What I meant by other file, is perhaps there is corruption in another fmp file that you did not recover, which is triggering corruption in the suspect file, or combining with latent corruption in the suspect file to cause a crash. Ie have you tried to recover ALL the files?

When you mentioned the XP case, with the pause between "switching files" it occurs to me that perhaps this script isn't corrupt, but something on the destination layout it is displaying is.

It could be a corrupt graphic that is causing the display software on the two different OSes to behave differently./badly.

Try deleting the layout and reconstructing it from scratch. Or, alternatively, try switching the layout being displayed as a result of the script to another layout, perhaps a blank one. If the crashing/pausing doesn't reproduce, at least you've narrowed it down to the layout.

On the other hand, Perhaps it is corrupt record data, try scanning through records in file 2 on that layout. When you run the script, is the active record in file 2 always the same?