Richard,

I saw your post in the other thread with a link to this article. Very informative (I just skimmed it, didn't read it all yet) ... I've got it bookmarked for future reference. I had forgotten about some of this stuff. Thanks! =)

~~Bonnie



>I found something that did fix my problem or at the very least a pointer in the right direction:
>
>http://www.codeproject.com/dotnet/UB_CAS_NET.asp?target=Code+Access+Security
>
>Hope this helps someone else in the future.
>
>Richard
>
>
>
>
>>Sorry that I couldn't be of more help, Richard. Security is not my strong point. I'm surprised that no one else jumped in to the rescue. <g>
>>
>>I hate starting over with stuff ... hopefully it's not too much, since it's a test project anyway. Good luck and let us all know if you find what caused the problem (well, hopefully you won't *get* the problem again <g>).
>>
>>~~Bonnie
>>
>>
>>
>>>No settings on the servers have changed. (Checked with the admin). I did find something about SQL Server 2000 access requiring full trust for debugging. Tried turning the SQL Server debugging off to no effect.
>>>
>>>At this point, I'm starting over. This is a test/learn project anyway. Thanks for all your help. I'll be back more than likely with other questions. (Hopefully not this one)
>>>
>>>Richard