Search results

  1. S

    Help with Database design!!!!!

    you may want to refer to the Access user manual just sayin....
  2. S

    Normalization and form design

    Oh ok! I wasn't using the quotation marks for the sql string Craig you have increased my knowledge exponentially and Im not sure how to thank you enough for your help and the time you've taken out of your schedule to instruct me as to what the solutions are to my questions.
  3. S

    Normalization and form design

    You're right, now that ive looked into it, seems like an UPDATE is a whole lot simpler and would do what im looking for. Private Sub cboActualAnswer_AfterUpdate() 'this is to take the combobox selection and put it into the txt box Me.txtActualAnswer = cboActualAnswer.Column(2) 'insert...
  4. S

    Normalization and form design

    Dim db As DAO.Database Dim rs As Recordset Dim strSQL As String If Me.QuestionID = "Q22a" And Me.txtActualAnswer = "0" Then 'If Mental Illness: None, then skip to Q23a Me.Dirty = False Set db = CurrentDb() Set rs = db.OpenRecordset("qryQuestionSkipQ22a", dbOpenDynaset) If Not...
  5. S

    Normalization and form design

    Genius! that worked like a charm, I have the textbox overlapping the combo, so you can't even tell there are two separate controls. Nothing like a little jerry-rigging The "On Enter" event for cboActualAnswer also worked, instead of the After update of the QuestionID
  6. S

    Normalization and form design

    Haha :D well the standard operating procedure here, is to create a 'flat-file'. It has been that way from long before I arrived, im just trying to adapt the various current projects and slowly progress to making them normalized. They usually follow the same type of formats that I have...
  7. S

    Normalization and form design

    Is it possible for this insert query to work (populate the table, and subsequently, the fields on a continuous form) In a database that does not have the relationships that you outlined in the example you showed me? This is a much much simpler survey design than the other ones I have posted...
  8. S

    One field = multiple one-to-manys

    Hello again, quick normalization/relationship themed question: picture of relationships is attached I have a main table which lists study name/number, and several other tables which list study information (recruit method, recruit criteria, etc) The study number is unique, there can be many...
  9. S

    NotInList for Cascading combos

    Alright thanks Bob this must be it, I was trying to cut down on the amount of tables, because I only have 3 fields: the key (autonum), MethodType (rowsource for 1st combo), and MethodName (rowsource for 2nd combo), but since splitting them up into separate tables is going to make it work, id...
  10. S

    NotInList for Cascading combos

    Hi, I've searched quite a bit on these forums already to no avail, so I decided to post the question: I have two cascading combo boxes. They work fine. I added a NotInList function for the second combo box. Private Sub cboMethodName_NotInList(NewData As String, Response As Integer) Dim...
  11. S

    Normalization and form design

    ^^ This is awesome!! I'm a VBA total novice, (i only understood about 40-50% of the code at face-value) so Im amazed at a lot of the nuances in the code, for instance: I would have never realized that I had to use the Nz function, or the .Dirty, or a whole lot of other things! Not sure how...
  12. S

    Normalization and form design

    Alright, I see.... sometimes I forget its called a "relational" model for a reason. ps: the forms I made was just messing around for the purposes of pre-entering data
  13. S

    Normalization and form design

    Im assuming this master/child field is going to be PeopleSurveyID? On a side-note, shouldn't the "QuestionID" FK in tblPeopleSurveyAnswers instead be "SurveyQuestionID" ? That way the correct list of questions, depending on which survey, is related? Im struggling to view this in my head...
  14. S

    Normalization and form design

    Nice! this is a godsend CraigD Oh boy...that sounds like a blast. Ill go back to work then and update this post with some substance
  15. S

    Normalization and form design

    You're right, this particular project is a different one from the one I was talking about in that thread. It is along the same idea (survey), so I used your suggestions as more of a guideline. This DB is a little less complicated, due to not needed separate time points. There is only a person...
  16. S

    Normalization and form design

    The second part to my question is about what you alluded to in your last post, Pat.. How do I design the entry forms for this survey? This has been killing me! I'm trying to create a design where the user will enter the Study Number (unique ID of person filling out the survey), then, select...
  17. S

    Normalization and form design

    Alright I see what you mean about there being possible problems down the road. And I have also listened to the advice of not using lookups at the table level. Your point about never entering data into a table though... I am creating this database with the intent on the user only entering...
  18. S

    Normalization and form design

    Thanks for the input Pat! To be honest I was debating whether or not to use Autonumber for the PK, or my own manually entered PK. The reason I used my own manual PK, is both for easy reference, (autonumbers aren't always in sequence, so it would be a pain in the butt to enter in the...
  19. S

    Normalization and form design

    Hello! Attached are two JPG files showing screenshots of my tables, and their relationships. I just wanted to see how my normalization looked to you guys and if im on the right track! This is for a survey type database with multiple separate surveys.
  20. S

    Design feedback

    Yes that is what I tried to explain in my first post, I need to design the table to store a person's diagnosis. Unfortunately I FAILED MISERABLY according to you, thanks for trying to help though, I think... Anyway, at first I did think of designing it as one table only! Then I started to...
Back
Top Bottom