Search results

Thank you Doc Man and dportas both for your comments. We did accomplish a design that was better suited for our organization here. As dportas mentioned, our initial usage of checkboxes to indicate accreditations was not necessarily unnormalized, but rather just kind of a pain to manage in MS...

The problem we run into is that facilities can have multiple accreditations. I might be missing something in your explanation, but I think the allowance of multiple accreditations means we'll have to come up with another approach. We're trying to normalize our structure by separating basic...

The only issue we have now is moving away from our previous, checkbox-centric, input forms (Access 2003) for the facility accreditations. I know this is a topic for another forum, but I thought since my case is already here, I might ask you once again for advice. After a day of trying, I feel...

Thanks for your response! It helps us know that we're on the right track to ironing out our structure. Many thanks. Just one question based on your advice. Our instinct is to avoid autonumbering tables that contain static information. For example, the facilities will not change. We have 33 and...

We're creating a database for a rural development project in the Philippines. The database tracks the accreditations of our medical facilities and in turn determines what equipment and quantities they must maintain for their accreditations. We have a functioning structure now, but we're...

Thanks! Got it with the following code: =Nz(DLookUp("[equipExpiry]","tblEquipAttributes","equipID = " & [txtEquipID]),"N/A") Is there a reason why Me.txtEquipID as a criteria would return #NAME? ? Does it have to do with my syntax (see below) or something else...

I'm trying to evaluate nulls returned from a DLookup. If a Null comes in, all I want to do is change the text displayed in a textbox to "N/A". If it's not Null, I want to display a value from DLookup. Below is the Control Source for the textbox...