[AccessD] SQL Question

We have no control over the source and thats the way it is.

We are bulding an SQL database to work with Windows security. We have to get 
our data into a single table. 

One of those jobs that just has to be done the way the security guys want it.

Martin


Quoting "Heenan, Lambert" <Lambert.Heenan at AIG.com>:

> Well to get the data laid out the way you suggest should only need a
> simple
> Cross Tab query, but (like everyone else) I have to ask "Why?" It looks
> like
> your two source tables have nicely normalized the data, but now you
> (or
> whoever is doing this HR thing) want to un-normalize it.
> 
> Also, why does the act of linking to another system require that you
> build
> this un-normalized table / query to work with it???
> 
> Lambert
> 
> > -----Original Message-----
> > From:	Mwp.Reid at Queens-Belfast.AC.UK
> [SMTP:Mwp.Reid at Queens-Belfast.AC.UK]
> > Sent:	Tuesday, June 24, 2003 1:07 PM
> > To:	accessd at databaseadvisors.com
> > Subject:	Re: [AccessD] SQL Question
> > 
> > has to be a table. We are linkinginto a Hunam Resource system and
> building
> > a 
> > security system.
> > 
> > Martin
> > 
> > Quoting Susan Harkins <harkins at iglou.com>:
> > 
> > > Martin, does this really have to be a "table" -- could you work with
> a
> > > report or form that looks like a table? I mean, are you really going
> to
> > > be storing the data in this format or do you just have some folks
> that
> > > want to see the data in this particular format?
> > > 
> > > Susan H. 
> > >   ----- Original Message ----- 
> > >   From: Martin Reid 
> > >   To: accessd 
> > >   Sent: Tuesday, June 24, 2003 11:32 AM
> > >   Subject: [AccessD] SQL Question
> > > 
> > > 
> > >   Have two tables 
> > > 
> > >   Table A Contains staff data, Name etc
> > >   Table B contains contact data
> > > 
> > >   Results of join as expected
> > > 
> > >   Staff Member A  Telephone Number 1
> > >   Staff Member A Telephone Number 2
> > >   Staff Member A Telephone Number 3
> > > 
> > >   And so on
> > > 
> > >   What I need to do is to flatten this out and create a single
> table
> > > 
> > >   Staff Member A     Phone Number 1     Phone Number 2     Phone
> Number
> > > 3 etc
> > >   Staff Member B      Phone Number 1    Phone Number 2
> > > 
> > >   We dont knwo how many numbers will exist for each member of staff
> but
> > > the Max will be 5 and I must end up with a single table containing
> the
> > > data.
> > > 
> > >   Need this to work in Access and SQL Server 2000
> > > 
> > >   Martin
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> >
> --------------------------------------------------------------------------
> > ----
> > > 
> > > 
> > >   _______________________________________________
> > >   AccessD mailing list
> > >   AccessD at databaseadvisors.com
> > >   http://databaseadvisors.com/mailman/listinfo/accessd
> > >   Website: http://www.databaseadvisors.com
> > > 
> > > 
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>