All I can say is to submit it to Microsoft. It's got to be something in that code or you've reached some kind of resource boundary.


>>I don't know what else to tell you, then. Like I said, I've seen this and know only that it's related to repeated build-run-rebuild-rerun cycles during development. In my case, running my reset environment macro after each run seems to avoid it. Your situation must be different.
>
>It is really buggy. Check this out.
>
>The following works:
>
>

>loImage9=CreateObject('Image')
>loImage9.Picture='Undo.gif'
>loImage10=CreateObject('Image')
>loImage10.Picture='Close.gif'
>loImage11=CreateObject('Image')
>loImage11.Picture='FirstDisable.gif'
>loImage12=CreateObject('Image')
>loImage12.Picture='NextDisable.gif'
>return
>*loImage13=CreateObject('Image')
>*loImage13.Picture='PreviousDisable.gif'
>

>
>I can enter VFP, build, run, build, run, etc.
>
>But, having this code:
>
>

>loImage9=CreateObject('Image')
>loImage9.Picture='Undo.gif'
>loImage10=CreateObject('Image')
>loImage10.Picture='Close.gif'
>loImage11=CreateObject('Image')
>loImage11.Picture='FirstDisable.gif'
>loImage12=CreateObject('Image')
>loImage12.Picture='NextDisable.gif'
>*loImage13=CreateObject('Image')
>*loImage13.Picture='PreviousDisable.gif'
>return
>

>
>I can enter VFP, build, run, build and VFP freezes.
>
>This is non sense.