Re: Referincing Fields
- From: "Jeff Boyce" <nonsense@xxxxxxxxxxxx>
- Date: Fri, 6 Mar 2009 08:27:06 -0800
Kat
I'm not sure I understand enough about what you have and what you want to do
to offer any specific suggestions.
Please note that you are not limited to continuing to use the existing data
store if it makes what you want to do more difficult. Have you considered
creating a new Access application and "pointing" at the existing data for a
starting point?
Regards
Jeff Boyce
Microsoft Office/Access MVP
"Kat" <Kat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:94FF1128-27C9-4CF2-8C8D-710B60A4463B@xxxxxxxxxxxxxxxx
I am importing data into a table and the design is terrible but as I don't
have access to the original source so I am stuck with it. Each record is
for
a single associate working in a certain path on a particular day so my
table
ranges in the 10s of thousands. Each path has a unique combination of
process and function names with units rolling up under several different
fields named according to the type of unit it is counting, such as
StowCases,
PickPallets or PickEACH, but I am only interested in using one of the
fields
depending on the path and there are about 50 of these types of fields I am
trying to wade through. Because the paths have units in multiple fields I
can't just add them. Is there a way in SQL or using the interface to
create
a query that will create a single units field in my query that will
reference
a different field within the imported table depending on the process and
function names in that particular record. I want to avoid using an iff
statement as I am trying to make this available to several different sites
across our network and they may need to add or remove paths which would be
a
lot easier with a seperate table with a relationship to the import rather
than going in and trying to edit a nested Iff statement(I currently have
21
different paths that I need to evaluate).
I have a table is set up that has the process name, function name and the
field/unit name that is in the imported table.
.
- Follow-Ups:
- Re: Referincing Fields
- From: Kat
- Re: Referincing Fields
- References:
- Referincing Fields
- From: Kat
- Referincing Fields
- Prev by Date: Referincing Fields
- Next by Date: Re: memory monitor
- Previous by thread: Referincing Fields
- Next by thread: Re: Referincing Fields
- Index(es):
Relevant Pages
|