>>I’ll look into that. I’m not familiar with the code access security topic.
>
>CAS assigns security to code (an assembly) based on evidence (zone, strong name, etc). Your code can demand that the calling code have a set of permissions before it executes or throw a security exception.

Let me rephrase my original response.
I'll "have someone" look into that. <g>

Actually I'm beginning to think that I should really make a separate assembly with the data access stuff and set the property in question as internal. For now I think I'll let the visibility issue slide.
I just don't like doing small applications with separate projects for everything but I think that is probably the best way to address this.

Thanks,