Hi Lynda,

Does your new code touch the array at all?

I only ask because you say you "I never use them". Some array functions return or use element# as opposed to regular subscripts.
Just thinking that could be a contributor to the issue (in case you didn't notice when coding).

good luck


>The scatter to array occurs in only one program called when the record is first viewed. It is nowhere near the locations where data often goes missing. I tend to focus on the error after the "new" routine just because I'm a bit sensitive that my code may have broken their ancient app <g>. That isn't the only place data disappears though. I tend to blame the problem on editing in arrays--probably because I never use them. I have never had data go missing from a View for example. Also, any "save" routine I've written only saves modified fields rather than overwriting every field in the table each time the record is viewed! This app doesn't use PEMs. Everything is in a program---somewhere--that is never called directly (as in by name.) The less I have to modify it the better I feel.
>
>I think you've made a good poinit Thomas. I would really like to modify the code gradually--charging them for it a bit at a time. I've actually been looking for a way to do that. But, the thing I really want to get rid of first and foremost is the arrays! To move the code into the Properties, Events and Methods of the forms (so one might have a chance of finding it!) and to convert editing to Views or Cursor Adaptors would be a major and far-reaching change. I can't envision starting with anything less... Perhaps I can no longer see "the forest for the trees."