Well after testing all day long and reading everything I could get my hands on I think I found a solution to my problem. Actually I'm not sure if I have just patched the problem or not since I cant find a logical reason why it works. I decided to add another global to the program and at the time the handle for the list is created I decided to make variable gTest& = gList&. I figured that if the pointer was nil then the pointer would no longer have the same address as it was originally assigned. I also figured once I returned an error I could check gTest& against gList&. Once the program ran I never got error. Of course this led me to believe that I had somehow trashed the variable gList& and gTest& was somehow just holding my program together. This is how its setup in the program DIM gList& DIM gTest& END GLOBALS I removed gTest& and the nil master pointer errors occured again. This time I decided to reverse the order of the variables to see if my hypothsis was correct. DIM gTest& DIM gList& END GLOBALS I ran the program again but I didnt get an error messages. Since gList& is the last global, no reason why it shouldnt have been trashed if that was the original problem. Now two questions: 1. Can anyone else reproduced the same symptoms. 2. Is there a logical explanation for what just happened. Thanks, W.