Referencing a table w/ a variable

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Robert Jarrett

    Referencing a table w/ a variable

    Trying to resolve what seems a complicated issue (to me); will simplify
    description of issue w/ an analogy:
    A -- 5 tables - Memories, engrams, P (persons), L (locations), and T
    (things). All start with two identicle fields: Code (txt5-Key) and
    Description (txt 25) but all have different numbers of other fields that are
    heavily used in other forms and purposes; BUT,
    B -- Memories = main table -->has some data unique to itself but then other
    data links to varied numbers and types of other files; hence, engrams (many
    memories)
    C -- Engrams = the "neural links" to numbers of Persons (with birthdays
    etc), locations (w/ coordinates etc) and Things (with owners etc); have a
    unique ID key but then only three fields a tblMemory code a tblName (ie P, L
    or T) and a tblCode
    D -- tbls P, L and T all begin w/ unique keys of 5 txt characters followed
    by description field.
    E -- Need a form to be able to data entry "memories" with their varied
    numbers of "engram" links to the P, L and T tbls
    F -- THE PROBLEM: would like to present a subtable with running list of
    already selected "engrams" and have either: (acceptable) two control fields
    one to lookup the acceptable table names which would then autofill a second
    control lookup field with possible choices (their code and descriptions); or
    (better) a FROM list on the left (perhaps tabbed for the file types) and a
    TO list on the right with a > and a < button between. either double
    clicking (or highlight and select ">") the choice on the left would move
    it's code and name into the TO list on the right [we've all seen these
    choice boxes]. of course when the choices are finished a "save" or "cancel"
    will update and show the main form again.

    I've been at this for several weeks and can't seem to be able to figure out
    the code - or possibly there's a better way to organize the approach i'm
    overlooking in my Access naiveté.

    Much gratitude for your help
    DJ


Working...