Myrl,

It's hard to say what causes a problem like that.

If you are opening a child form from a method of a private DS form, you can set the child form DS to Default DS and it will open up within the private DS of the parent form. This way you don't have to screw around with DS numbers.

>This is my first foray into Universal Thread, and I am not sure how this works, but here goes.
>
>I have an application written in VFP 5.0. There is one section of code which, from time to time, results in an invalid page fault. When run on the NT, the error seems to be either "Access Violation" or some reference to being unable to read memory. Are these equivalent?
>
>What kinds of things are known to cause this error? Are there a list of things which can be done to avoid them?
>
>Originally, we were passing the data session to a new form but discovered that caused all sorts of errors. When we changed it to just pass a snapshot which could be opened in the new form, many of the errors were corrected, but some linger.
>
>Any help in this would be very much appreciated! Are there resources which discuss this problem?