Mac OSX & OS9 - FMP6

I have never seen this error before.  Have you?

When i get this message
Filemaker's only option is to quit.  All files are left improperly
closed.  It knocks a server out totally.  When i first saw it i
assumed the hard drive format was bad, so i reformated the hard
drive.  While i was accomplishing this, i moved the database set to a
different computer and ran it as a multi-user shared file.  And low
and behold, i saw the same error and it went down again.  I have
since seen it on another computer.  It must be damage to one of the
files.  I suspect it could have been caused when i accessed some
field definitions across the network.  I was the only user, but i am
superstitious about this and wish i had never done it.

There are some new files that i resurrected from an old FP4 solution
that i suspect.  It usually happens when interacting with one of
them.   Generally the computer, especially any hosted clients, slows
down more and more, as if the host was having difficulty writing,
then when things really gum up i get the error.

 I carefully cloned, recovered the clone, and re-imported each
suspected file as well as the master file.  But i saw it again today.
One time it disrupted OS9 so badly that even after Filemaker had quit
the MacOS could not write any file buffers and it kept throwing up
error windows to the Finder, till i rebooted.  Serious stuff.

I have not been able to reproduce it systematically.

Has anyone seen an error like this before?

I cannot image how a damaged file structure could disrupt the OS?

Any other suggestions for tracking this erratic, sinister monster and
killing it?

--

------
Terry McDanel


terry dot mcdanel  at  mpls dot k12 dot mn dot us
=======================================================================

I experienced the same problem with a corrupted file (MacOS 8.6 & 
Windows 2000, FMP 5.5). In my case, the suspect file would open fine by 
itself, but not as part of the solution to which it belongs. The problem 
*seems* to have been solved by recovering the file in question, 
replacing it (in the solution) with a fresh, blank back-up copy, and 
finally importing the data from the recovered file to the fresh one.

Hope this helps.

Luis.
--
Luis Melgoza  -Ardinet      lumelATardiDOTnet       http://www.ardi.net     
    
Custom Database Applications & Interactive Web Site Development
PO BOX 1076 Lexington VA 24450-1076 USA           Ph & Fax: 540-464-5994
 "21st. Century Solutions for the Rest of US" Mexico  *  US  *  Canada

In article <231020031349233234%tmcdanel@nospam.iname.com>,
 Terry McDanel <tmcdanel@nospam.iname.com> wrote:

> Mac OSX & OS9 - FMP6
> 
> I have never seen this error before.  Have you?
> 
> When i get this message
> Filemaker's only option is to quit.  All files are left improperly
> closed.  It knocks a server out totally.  When i first saw it i
> assumed the hard drive format was bad, so i reformated the hard
> drive.  While i was accomplishing this, i moved the database set to a
> different computer and ran it as a multi-user shared file.  And low
> and behold, i saw the same error and it went down again.  I have
> since seen it on another computer.  It must be damage to one of the
> files.  I suspect it could have been caused when i accessed some
> field definitions across the network.  I was the only user, but i am
> superstitious about this and wish i had never done it.
> 
> There are some new files that i resurrected from an old FP4 solution
> that i suspect.  It usually happens when interacting with one of
> them.   Generally the computer, especially any hosted clients, slows
> down more and more, as if the host was having difficulty writing,
> then when things really gum up i get the error.
> 
>  I carefully cloned, recovered the clone, and re-imported each
> suspected file as well as the master file.  But i saw it again today.
> One time it disrupted OS9 so badly that even after Filemaker had quit
> the MacOS could not write any file buffers and it kept throwing up
> error windows to the Finder, till i rebooted.  Serious stuff.
> 
> I have not been able to reproduce it systematically.
> 
> Has anyone seen an error like this before?
> 
> I cannot image how a damaged file structure could disrupt the OS?
> 
> Any other suggestions for tracking this erratic, sinister monster and
> killing it?
> 
> --
> 
> ------
> Terry McDanel
> 
> 
> terry dot mcdanel  at  mpls dot k12 dot mn dot us
> =======================================================================