Search results

  1. M

    best way to deal with names?

    presumably this isn't logical operations. Is this where a null basically means 'unknown' so anything + 'unknown' must also be null which for practical purposes is a string with nothing in it?
  2. M

    can't understand access behaviour with relationship creation

    Thanks stopher. For the full name I'm actually using 2 fields from the same table rather than 2 separate ones. Is that the same? I think I'm gradually seeing the light. The wholename field in the appointments table is a number datatype. Whichever method you use to select the name displays the...
  3. M

    best way to deal with names?

    so if any of the fields are null the result leaves out the whole contents of those brackets?
  4. M

    can't understand access behaviour with relationship creation

    You must be psychic. I think you've answered another question I posted separately. So, in the appointments table I don't use two separate name fields, just one for the whole name? I'm not quite sure why that now means I can join to the therapistid field and nit their individual first an last...
  5. M

    best way to deal with names?

    In my database I will have a table of names (e.g. for customers) and in some places I will be using the whole name and in some cases just the first name (e.g. 'Dear John'). I assume this means the first and last names have to be entered in their own fields. In which case, what's the easiest way...
  6. M

    can't understand access behaviour with relationship creation

    Thanks - I'm going away to grapple a bit with that. I am using unique ID fields for both tables. I don't quite understand how I get the therapists name to appear in the name field in the appointments table without using a lookupwizard. Do you put a number in there instead of looking up the...
  7. M

    can't understand access behaviour with relationship creation

    wow - you guys are answering faster than I can ask!
  8. M

    can't understand access behaviour with relationship creation

    I appreciate your comments, stopher but now that leaves me slightly confused again. Relationships aren't working the way I thought they did - please could you have a bash at answering my questions in the original post to see if it throws some light for me?
  9. M

    can't understand access behaviour with relationship creation

    Wow - thanks for that. Must be one of the most useful threads I've seen on the topic. Much is made of access being a relational database so when you wrote that creating relationships could wait until later or may be unnecessary at all then these things seemed at odds with each other. Then your...
  10. M

    can't understand access behaviour with relationship creation

    Wow - now I'm confused.... If you don't need them, why did access create them for me? And why do we need relationships at all in that case?:confused:
  11. M

    can't understand access behaviour with relationship creation

    Oh - one other question. I tried deleting the relationships that access created and the lookup wizards still work so why are the relationships needed for this?
  12. M

    can't understand access behaviour with relationship creation

    I’m in the early stages of learning access and I’m hoping someone can explain what’s going on here for me. I created 2 tables, appointments and therapists. The therapists table will provide the name of the therapist to go into the appointment table. I created a relationship between the 2...
  13. M

    primary and foreign keys

    Thanks, Minty. Appreciate the advice.
  14. M

    primary and foreign keys

    .... and I have quite a few of them! This is the one topic they all explain very poorly or gloss over. I've been a fairly advanced excel user for a long time and I think its shaped my thinking in a way that's unhelpful when understanding access.
  15. M

    primary and foreign keys

    once again, many thanks. Ithink plenty of sstrong coffee and i'll be spending the day trying to get my head around all that.....
  16. M

    primary and foreign keys

    Oh, btw, you are quite right about NHS numbers and hospital numbers as primary keys - patients just never remember them or get them mixd up so they aren't really safe to use.
  17. M

    primary and foreign keys

    How do you decide which should be the master table? In this case i wouldhave thought the appointments table should be the master as all the other tables feed into it? Wow - that's fantastic. I really appreciate your help. I think i learnt more from your one post than from an afternoon of...
  18. M

    primary and foreign keys

    Thanks for that. May I ask what you mean by 'TPatients.PatientID. (Nhs)'? How do you decide which should be the master table? In this case i wouldhave thought the appointments table should be the master as all the other tables feed into it?
  19. M

    primary and foreign keys

    I'm an access (2007) novice and I'm trying to grapple with table relationships. I understand the concept of dividing data into different tables to avoid repetition but I just can't quite get a grip on primary and foreign keys. I think the bit I'm missing is how to choose the foreign key. I...
Back
Top Bottom