How does she access this file that is on a novell server? If she is accessing a file in a shared directory by finding and opening the file, she risks damage to the file. A file located on a remote server should be hosted by Filemaker Pro or FileMaker Server on that machine, then the users should launch FileMaker on their machine and use Open Remote to access it.
I'd check the available space on the users C: drive (System partition) to see how much unused space exists on it. FileMaker creates a temp file that needs space inorder for the user to use the database file. I'd also check the server's hard drive for available space as well.
She maybe accessing the file by double clicking it. Someone else made a shortcut for her probably to her DB. we have very few filemakerPro users as it's not really supported on campus and no server portion. She is the only one using the database. The amount she is allocated on Novell is 1 GB and has over 600 MB left. I thought that the tempfile was made on the C: drive and not the novell server. What's the formula, if there is one that dictactes the size of the temp file? Her C drive is't that full and it's not partioned except for the Dell diagnostics partition which is very small. The problem is intermittent. she states 3 times in 6 months.
The temp file is on the C:drive, but you still need room for the file to grow on the server's drive so you have to check capacity in both places.
Opening the file on a shared directory as the only user--while much safer than with multiple users--could still corrupt the file. Note also that any server back up software that regularly backs up this file may be creating corrupted backups if the file is open at the time the software backs it up.
Thus, just to be safe, you might want to run a recover on the file to see if any issues are reported. (And you may want to do a check disk on her computer to make sure that it's in good shape as well.)
Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
I know what I am going to recommend to the customer. If there are further issues I will le tyou know.