terrald said:
>   Then as I append elements, 
>   I actually insert them after the last one that was legitimate.  
>   The fn inselement path is not changed....
>   only had to do the empty rows and then insert....
>   probably I will do a replace instead of an insert after the last good one 
>   but right now.....I can suck up the empty four blanks 
>   (they look better than the crash)

i saw that the subject on this was "lmcd errors",
but i know terrald has also been having str# problems,
so i'll send this out anyway.  if it's not relevant, please ignore...

terrald, something you say here makes me think your problems 
might be due to confusion between appending, inserting, and replacing:

if a str# has only 10 elements (for example),
you will mess up that str# very badly
if you try to "insert" element 16 (for example).

(this could be either because you actually want an element 16, but 
it's more like that you have a bug that's causing you to overshoot,
which is the problem that i was having, and only became aware of 
when i tracked the changes that i was actually making to the str#,
and not the ones that i _thought_ i was making.)

you should also know that str# will never be any good again
(though you may not realize it's damaged without close scutiny),
so you need to actually delete it so it doesn't cause more trouble.

not only that, but writing outside the bounds of the str#
could well be the cause of the crashes you're experiencing.

in the example above, you would have to "append" (not "insert")
6 elements after the original 10 to get you up to 16.

"append" means to add an item right after the last existing element.
"insert" means to add an item in front of an existing element.

also note that the "replace" function actually 
does a "delete" and then an "insert" (or vice versa, can't remember)
so it is susceptible to the same type of problem.
(that is, you can't "replace" element 16 if you only have 10 elements.)

one of the p.g. str# functions tells you how many elements in a str#,
so you can use this to make sure you're calling the right function.

i'm sorry this sounds so simplistic -- 
i did see the m.d. after your name --
but sometimes the simplest bugs are the hardest to find.

-bowerbird