C
celticangyl
I am curretly putting together a vba module in word to transfer several
hundred reports into an existing Access database of these same, newer
version reports. I have several issues I'm pondering at the moment, the
first and most troublesome at the moment involves Lookup's.
In my main table, I have a Lookup to Employees and a Lookup to
fractional fuel quantities. My question on this is, do I have to pull
the employees recordset, make a match and then export the associated
index number when exporting the main table? Or is there an easier way
where I can look this up and store it in one fell swoop?
My second question involves multi-layered tables, for each daily
report, there is a daily report number, DAR-YYYY-MM-DDx and for each
daily report there is a list of activities. Can I just upload the DAR
number in the main table as a single entry and then upload the DAR
number with each Activity entry and still maintain proper associations
when queried? looking at it from a human perspective this seems to
work, however I am not fully aware of what code associations that
Access does in the background in addition to the like named data.
Thanks,
Brian
hundred reports into an existing Access database of these same, newer
version reports. I have several issues I'm pondering at the moment, the
first and most troublesome at the moment involves Lookup's.
In my main table, I have a Lookup to Employees and a Lookup to
fractional fuel quantities. My question on this is, do I have to pull
the employees recordset, make a match and then export the associated
index number when exporting the main table? Or is there an easier way
where I can look this up and store it in one fell swoop?
My second question involves multi-layered tables, for each daily
report, there is a daily report number, DAR-YYYY-MM-DDx and for each
daily report there is a list of activities. Can I just upload the DAR
number in the main table as a single entry and then upload the DAR
number with each Activity entry and still maintain proper associations
when queried? looking at it from a human perspective this seems to
work, however I am not fully aware of what code associations that
Access does in the background in addition to the like named data.
Thanks,
Brian