Q. Why do you need each volunteer to be separately logged in? Do you need to keep track of who let in whom? Assuming you're not too concerned about someone trying to steal or knacker the database then the type of security doesn't really matter - integrated or not that is. You could do something as simple as asking them to type in their name (selection from a drop down could be risky - what if someone volunteers in another user's place?) and then log that in the database. Disable the entry of the name on a login/logout button and bob's your uncle. ___________________________________________ .\\axxx (That's an 'M')

A+ my friend! Events are not the easiest thing to wrap your brain around. BTW, I might add that it's really not proper to include the text "Interface" in an object. (There is an actual .Net object called an interface) The subject of an interface is entirely for another time but it is a very helpful tool. I would suggest: "SQLXmlEditor" or "SQLXmlViewer" depending on it's functionality. The mind is like a parachute. It doesn’t work unless it’s open.