Recent content by mikulas

  1. M

    unique identifier across multiple "sister" tables

    Thanks, Galaxiom, for the wise words. Since I have no VBA experience, then it looks like I will begin with a primer before asking specific questions here. How did you know? j/k
  2. M

    unique identifier across multiple "sister" tables

    @lagbolt: Now that you've explained it, the relationships seem rather obvious. Sorry I didn't see that before... @Galaxiom: Unfortunately VBA is not my suit at all. But thank you for the outline you gave in your last post -- I agree, avoiding a plethora of forms for different artifact types...
  3. M

    unique identifier across multiple "sister" tables

    OK. But if the data type of the last field in the third table tblArtifactProperties pkArtifactPropertyAutonumberID fkArtifactAutonumberID 'Number fkPropertyAutonumberID 'Number PropertyValue 'Text, so that you can enter anything you need to. is set to "text", then what if I want to later sort...
  4. M

    unique identifier across multiple "sister" tables

    Thanks, Krystal. I certainly see how the structure you propose makes sense, but it seems like I would then have to enter info for each record by hand -- I already have fully populated tables in Excel, and it would take some fancy cutting-and-pasting to achieve tables directly importable into...
  5. M

    unique identifier across multiple "sister" tables

    I'm working on a database to store information about archaelogical artifacts. I have a number of different types of artifacts, such as beads, utensils, and ceramics. Each type has fields that pertain only to that type of artifact (e.g., circumference applies to beads, not utensils). But at the...
Back
Top Bottom