Just wondering if you remembered whenever you put code into forms methods to include a dodefault() so the default code would also run? I ran into that problem quite a few times. It would just slip my mind. It would be wonderful if whenever you modified a form's method, it would slip a dodefault() in there (just like the parameters) automatically. I would remark it out if I didn't want the default code to run also, but more often than not, I want to ADD my code, not replace the default code. I've converted a bunch of FPD26 forms, and afterwards, had to move stuff to where it goes aftewards of course. There are some links out there at MSFT on where the converter puts the FPD26 code and where you need to move it to when the converter is finished. I was always dissappointed with the results though, so I ended up rewriting the screens into VFP6/7 forms evertime. We finally decided to run the FPD26 screen's sprs instead until each screen could be redone in VFP and that has been the most successful.
Tracy

>Hi Andy.
> The problems that happened to use were actual unexpected problems and did not make sense for awhile. In fact it still doesn't make sense. They actually happened on non converted forms, not the converted forms. It was just that we were in the habit of using the load method for doing alot of work. The 1st catastrophy was just a call to a function to be sure the keyboard is clear and that the last key stroke is not recorded as a Enter. It worked until one day, under very specific and repeatable situations, it blew up. Even there it would work for 3 instances of the form and then blew. The move of the calls into the init works.....
> - Glen -