Those are the problems I encountered. This is caused by the SDT code run after ViewEdit is called by SDT. I like the idea of the ViewEdit form being non-modal, but I think ViewEdit should be passed a 3rd parameter so ViewEdit can start as a modal form if called by SDT.

>Mark,
>
>FWIW I encountered another problem, namely that you can't activate ViewEdit's Page3 or Page4 when it's been called by SDT. A cursor needed by ViewEdit is evidently not open where it should be, maybe due to some issue re the private data session used by SDT. I just e-mailed Steve on this.
>
>-Rick
>
>
>>Doug:
>>
>>Just downloaded SDT 5.1J update and read with interest the support for Steve Sawyer's ViewEdit utility. The utility is called correctly, however there is a bug. The problem is caused by ViewEdit not being a MODAL form so your validation code after calling ViewEdit runs as soon as ViewEdit is instanciated instead of closed. ViewEdit also does not use a Provate DS.
>>
>>I love the potential of the SDT hok into ViewEdit, so maybe you and Steve can work something out between your 2 products.
>>
>>Thanks.
>>
>>P.S. For those interested, Steve's ViewEdit tool is available free at http://www.stephensawyer.com