>>Personally I would quit using the active x control and use native VFP commands and objects. I have a schedule class that I wrote which is not hard to do.
>
>Greg,
>
>This is a very complex form that has been in the production for many years. I am not sure what exactly has changed or why they are reporting crashes now, did we get them before or not.
>
>In any case, it's not possible to change that form and we're sun-setting this application anyway (the re-write of that application is going on now and I am part of the developers team working on the re-write).

I hear what you are saying, but wrapping the API and exchange for pure vfp code is a valid DEBUG approach as well sometimes - as is the backtrack in Source Control to find the earliest occurrence. BOTH approaches are time consuming, so I'd lop the error to managment to decide if a fix is needed considering potential cost.