To the people who know more than me...

I'm running SharePoint Service 2.0 and currently have linked tables in
Access 2003 pointing to 10 lists. The structure of these lists are exactly
the same.

I need a way to merge all the information from the 10 tables into 1 table
and make a way for this to happen on a daily at a given time.

Thank you in advanced for the help!

"IT Challenged" <IT (E-Mail Removed)> wrote in message
news:9531726F-4A66-4493-A8D8-(E-Mail Removed)...
> To the people who know more than me...
>
> I'm running SharePoint Service 2.0 and currently have linked tables in
> Access 2003 pointing to 10 lists. The structure of these lists are exactly
> the same.
>
> I need a way to merge all the information from the 10 tables into 1 table
> and make a way for this to happen on a daily at a given time.

Are you familiar with UNION and UNION ALL Queries/SQL Statements? That will
allow you to concatenate the information from all ten (linked tables)...
then you could convert that into an Append or a Make-Table Query to create
the new table. As these would be stored Queries, it would be simple to
execute them from VBA code.

Larry Linson
Microsoft Access MVP

I would reccomend staying away from MDB against Sharepoint; it is too
slow to be useful.

You should keep your data in SQL Server; and you can use SQL Server
tools in order to get to this data in a more logical format.

in other words; why worry about pulling 10 lists-- and jamming them
back into one table-- when they are already stored in one table on the
sharepoint side?

-Tom



Larry Linson wrote:
> "IT Challenged" <IT (E-Mail Removed)> wrote in message
> news:9531726F-4A66-4493-A8D8-(E-Mail Removed)...
> > To the people who know more than me...
> >
> > I'm running SharePoint Service 2.0 and currently have linked tables in
> > Access 2003 pointing to 10 lists. The structure of these lists are exactly
> > the same.
> >
> > I need a way to merge all the information from the 10 tables into 1 table
> > and make a way for this to happen on a daily at a given time.
>
> Are you familiar with UNION and UNION ALL Queries/SQL Statements? That will
> allow you to concatenate the information from all ten (linked tables)...
> then you could convert that into an Append or a Make-Table Query to create
> the new table. As these would be stored Queries, it would be simple to
> execute them from VBA code.
>
> Larry Linson
> Microsoft Access MVP

Hello Punjab,

I guess you didn't read my name on this post... =)

"punjab_tom" wrote:

> I would reccomend staying away from MDB against Sharepoint; it is too
> slow to be useful.
>
> You should keep your data in SQL Server; and you can use SQL Server
> tools in order to get to this data in a more logical format.
>
> in other words; why worry about pulling 10 lists-- and jamming them
> back into one table-- when they are already stored in one table on the
> sharepoint side?
>
> -Tom
>
>
>
> Larry Linson wrote:
> > "IT Challenged" <IT (E-Mail Removed)> wrote in message
> > news:9531726F-4A66-4493-A8D8-(E-Mail Removed)...
> > > To the people who know more than me...
> > >
> > > I'm running SharePoint Service 2.0 and currently have linked tables in
> > > Access 2003 pointing to 10 lists. The structure of these lists are exactly
> > > the same.
> > >
> > > I need a way to merge all the information from the 10 tables into 1 table
> > > and make a way for this to happen on a daily at a given time.
> >
> > Are you familiar with UNION and UNION ALL Queries/SQL Statements? That will
> > allow you to concatenate the information from all ten (linked tables)...
> > then you could convert that into an Append or a Make-Table Query to create
> > the new table. As these would be stored Queries, it would be simple to
> > execute them from VBA code.
> >
> > Larry Linson
> > Microsoft Access MVP
>
>

Thanks Larry!!! I'm researching these types of queries and should be able to
implement your suggestions. Your reply was exactly what I was looking for!

"Larry Linson" wrote:

>
> "IT Challenged" <IT (E-Mail Removed)> wrote in message
> news:9531726F-4A66-4493-A8D8-(E-Mail Removed)...
> > To the people who know more than me...
> >
> > I'm running SharePoint Service 2.0 and currently have linked tables in
> > Access 2003 pointing to 10 lists. The structure of these lists are exactly
> > the same.
> >
> > I need a way to merge all the information from the 10 tables into 1 table
> > and make a way for this to happen on a daily at a given time.
>
> Are you familiar with UNION and UNION ALL Queries/SQL Statements? That will
> allow you to concatenate the information from all ten (linked tables)...
> then you could convert that into an Append or a Make-Table Query to create
> the new table. As these would be stored Queries, it would be simple to
> execute them from VBA code.
>
> Larry Linson
> Microsoft Access MVP
>
>
>

what do you talk of?

-Tom


IT Challenged wrote:
> Hello Punjab,
>
> I guess you didn't read my name on this post... =)
>
> "punjab_tom" wrote:
>
> > I would reccomend staying away from MDB against Sharepoint; it is too
> > slow to be useful.
> >
> > You should keep your data in SQL Server; and you can use SQL Server
> > tools in order to get to this data in a more logical format.
> >
> > in other words; why worry about pulling 10 lists-- and jamming them
> > back into one table-- when they are already stored in one table on the
> > sharepoint side?
> >
> > -Tom
> >
> >
> >
> > Larry Linson wrote:
> > > "IT Challenged" <IT (E-Mail Removed)> wrote in message
> > > news:9531726F-4A66-4493-A8D8-(E-Mail Removed)...
> > > > To the people who know more than me...
> > > >
> > > > I'm running SharePoint Service 2.0 and currently have linked tables in
> > > > Access 2003 pointing to 10 lists. The structure of these lists are exactly
> > > > the same.
> > > >
> > > > I need a way to merge all the information from the 10 tables into 1 table
> > > > and make a way for this to happen on a daily at a given time.
> > >
> > > Are you familiar with UNION and UNION ALL Queries/SQL Statements? That will
> > > allow you to concatenate the information from all ten (linked tables)...
> > > then you could convert that into an Append or a Make-Table Query to create
> > > the new table. As these would be stored Queries, it would be simple to
> > > execute them from VBA code.
> > >
> > > Larry Linson
> > > Microsoft Access MVP
> >
> >

IT Challenged wrote:
> Hello Punjab,
>
> I guess you didn't read my name on this post... =)
>
> "punjab_tom" wrote:
>
>> I would reccomend staying away from MDB against Sharepoint; it is too
>> slow to be useful.
>>
>> You should keep your data in SQL Server; and you can use SQL Server
>> tools in order to get to this data in a more logical format.

Don't mind him, hon. His solution for everything is to use ADPs and SQL
Server. Cell phone battery died? Use SQL Server. Got indigestion? Switch
to ADPs. Neighbor's dog kept you up all night barking? Should've used SQL
Server!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200611/1

Thanks Granny, we are all learning at our own pace. I have SQL query and
design classes scheduled for February!!! Yay!

"Granny Spitz via AccessMonster.com" wrote:

> IT Challenged wrote:
> > Hello Punjab,
> >
> > I guess you didn't read my name on this post... =)
> >
> > "punjab_tom" wrote:
> >
> >> I would reccomend staying away from MDB against Sharepoint; it is too
> >> slow to be useful.
> >>
> >> You should keep your data in SQL Server; and you can use SQL Server
> >> tools in order to get to this data in a more logical format.
>
> Don't mind him, hon. His solution for everything is to use ADPs and SQL
> Server. Cell phone battery died? Use SQL Server. Got indigestion? Switch
> to ADPs. Neighbor's dog kept you up all night barking? Should've used SQL
> Server!
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...ccess/200611/1
>
>

Hi Tom, we are implementing SharePoint Portal early next year which will use
our SQL backend. I'm still learning SQL and how to query so for now, i'll use
Access. Thank you for your post!!!

"punjab_tom" wrote:

> I would reccomend staying away from MDB against Sharepoint; it is too
> slow to be useful.
>
> You should keep your data in SQL Server; and you can use SQL Server
> tools in order to get to this data in a more logical format.
>
> in other words; why worry about pulling 10 lists-- and jamming them
> back into one table-- when they are already stored in one table on the
> sharepoint side?
>
> -Tom
>
>
>
> Larry Linson wrote:
> > "IT Challenged" <IT (E-Mail Removed)> wrote in message
> > news:9531726F-4A66-4493-A8D8-(E-Mail Removed)...
> > > To the people who know more than me...
> > >
> > > I'm running SharePoint Service 2.0 and currently have linked tables in
> > > Access 2003 pointing to 10 lists. The structure of these lists are exactly
> > > the same.
> > >
> > > I need a way to merge all the information from the 10 tables into 1 table
> > > and make a way for this to happen on a daily at a given time.
> >
> > Are you familiar with UNION and UNION ALL Queries/SQL Statements? That will
> > allow you to concatenate the information from all ten (linked tables)...
> > then you could convert that into an Append or a Make-Table Query to create
> > the new table. As these would be stored Queries, it would be simple to
> > execute them from VBA code.
> >
> > Larry Linson
> > Microsoft Access MVP
>
>

IT Challenged wrote:
> Thanks Granny, we are all learning at our own pace. I have SQL query and
> design classes scheduled for February!!! Yay!

You'll probably find it challenging but once you get the hang of it, you'll
find out how powerful it is ... and *you've* got that power at your
fingertips! Best of luck to you.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200611/1