Looks good.... Only suggestion I would make is to check the specific email address first, then the domain...
That way if the user is allowed, but the domain is blocked, then you never get to having to process the domain check. You only really need to do the domain check if there isn't a specific block/unblocked instance for the user. Regards Stephen ----- Original Message ----- From: "Erika L. Walker-Arnold" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 02, 2002 11:14 AM Subject: [ cf-dev ] OT: DB help > Setting up a table or two to handle an administrative task. > > I have an app where user's register for access. > > The client wants the ability to block whole email address and/or domains > (i.e. Yahoo.com). > > For some reason (prolly cause it's the end of the week and all I wanna > do right now is hit the pub) I can't get my head around the simple table > structure. I have this right now, but is it enough? > > BU_ID int 4 > BUCOMP_ID char 10 > BUADDRESS varchar 255 <--- address or domain > BUYESNO bit 1 <---- block or allow > BUBYWHOM int 4 <---- user who setup block > BUDATEADDED datetime 8 > > My logic is that they'll enter a domain name (i.e. Yahoo.com) but if > they have a legit user like [EMAIL PROTECTED] .. Then they can enter > the user's email in the same Block-a-User form, but check off allow. > > In my reg check, I'll check first for an instance of the domain, ... And > if the domain does exist .. Check the *allowed users (BUYESNO EQ 1)* > next to ensure the filtering is correct. > > Before I set out to build this dandy little feature .. I wanted some > second opinions. > > Erika > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
