multi-source odbc to single table

you should learn how to DTS the data you need (at summary level, I
would assume).

using Access across _ANY_ type of network is not reccomended-- because
it's not stable.
when you're talking about different stores, I'm sure you're talking
about a WAN.

And Jet just doesn't run over a WAN.

If you want to use Access over a WAN, then you need to move to SQL
Server.
If you want to use Access over a WAN, then you need to move to SQL
Server.
If you want to use Access over a WAN, then you need to move to SQL
Server.

-Aaron



On Dec 29, 1:49 pm, Royce wrote:
> I have two sources of data.  Server 1 and 2 that have the same type of data
> but for different stores.  Right now I have to pull the data seperately and
> then copy and paste in excel to merge into 1 file.  Makes the process slow.  
> Is there a way to link both sources and essentially have them one on top of
> another.  Another words pull them at the same time into 1 single linked table.
 >> Stay informed about: multi-source odbc to single table 

Okay, there is a good chance you can do that, or something like it, but we
ought to have a bit more information first.

When you say you are pulling data, several factors need to be clarified.
What sort of connection do you have to the servers? How is the data made
available to you? WHat does it mean to pull it down? And so on.

Rather than leap to a totally irrelevant suggestion, such as the one offered
by our friend Aaron, let's sort out what you are doing now.

Thanks.

"Royce" wrote in message

>I have two sources of data. Server 1 and 2 that have the same type of data
> but for different stores. Right now I have to pull the data seperately
> and
> then copy and paste in excel to merge into 1 file. Makes the process
> slow.
> Is there a way to link both sources and essentially have them one on top
> of
> another. Another words pull them at the same time into 1 single linked
> table.
>
 >> Stay informed about: multi-source odbc to single table 

Okay, there is a good chance you can do that, or something like it, but we
ought to have a bit more information first.
When you say you are pulling data, several factors need to be clarified.
What sort of connection do you have to the servers? How is the data made
available to you? WHat does it mean to pull it down? And so on.

Rather than leap to a totally irrelevant suggestion, such as the one offered
by our friend Aaron, let's sort out what you are doing now.

Thanks.

"Royce" wrote in message

>I have two sources of data. Server 1 and 2 that have the same type of data
> but for different stores. Right now I have to pull the data seperately
> and
> then copy and paste in excel to merge into 1 file. Makes the process
> slow.
> Is there a way to link both sources and essentially have them one on top
> of
> another. Another words pull them at the same time into 1 single linked
> table.
>
 >> Stay informed about: multi-source odbc to single table 

"a a r o n _ k e m p f" wrote:

> using Access across _ANY_ type of network is not
> reccomended-- because it's not stable.

Around Detroit, we don't like liars, squarehead. And what you said is a damn
lie. And, that makes you a damned liar.

> And Jet just doesn't run over a WAN.

Even my dumb wop barber knows you don't ODBC to another Access database. But
even he is smarter than a squarehead like you with solid bone between the
ears. You been knockin back too many beers to read, boy, or you just an
ignoramus?

> If you want to use Access over a WAN, then
> you need to move to SQL Server.

If you wasn't too drunk or too dumb to read, you'd know he's already using a
server database (doesn't have to be MS SQL Server, can use lots of them with
ODBC).

Mr. Kowalski
 >> Stay informed about: multi-source odbc to single table 

Walt Kowalski wrote:

>Even my dumb wop barber knows you don't ODBC to another Access database. But
>even he is smarter than a squarehead like you with solid bone between the
>ears. You been knockin back too many beers to read, boy, or you just an
>ignoramus?
>
> > If you want to use Access over a WAN, then
> > you need to move to SQL Server.
>
>If you wasn't too drunk or too dumb to read, you'd know he's already using a
>server database (doesn't have to be MS SQL Server, can use lots of them with
>ODBC).

Regretfully Aaron Kempf is psychiatrically ill as he is monomaniacal
on the subject of SQL Server and ADPs.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 >> Stay informed about: multi-source odbc to single table 

Please refrain from ethnic slurs. Perhaps "wop" has a new meaning in
contemporary slang, but if so I doubt I'm the only one who is not aware of
the changed usage.

"Walt Kowalski" wrote in message

> "a a r o n _ k e m p f" wrote:
>
> > using Access across _ANY_ type of network is not
> > reccomended-- because it's not stable.
>
> Around Detroit, we don't like liars, squarehead. And what you said is a
> damn
> lie. And, that makes you a damned liar.
>
> > And Jet just doesn't run over a WAN.
>
> Even my dumb wop barber knows you don't ODBC to another Access database.
> But
> even he is smarter than a squarehead like you with solid bone between the
> ears. You been knockin back too many beers to read, boy, or you just an
> ignoramus?
>
> > If you want to use Access over a WAN, then
> > you need to move to SQL Server.
>
> If you wasn't too drunk or too dumb to read, you'd know he's already using
> a
> server database (doesn't have to be MS SQL Server, can use lots of them
> with
> ODBC).
>
> Mr. Kowalski
>
 >> Stay informed about: multi-source odbc to single table 

Walt;

Sorry dude, but Jet doesnt' work over any network reliably, especially
WAN, Wireless, VPN, etc

-Aaron


On Dec 29 2008, 9:14 pm, Walt Kowalski
wrote:
> "a a r o n _ k e m p f" wrote:
>
>  > using Access across _ANY_ type of network is not
>  > reccomended-- because it's not stable.
>
> Around Detroit, we don't like liars, squarehead. And what you said is a damn
> lie. And, that makes you a damned liar.
>
>  > And Jet just doesn't run over a WAN.
>
> Even my dumb wop barber knows you don't ODBC to another Access database. But
> even he is smarter than a squarehead like you with solid bone between the
> ears. You been knockin back too many beers to read, boy, or you just an
> ignoramus?
>
>  > If you want to use Access over a WAN, then
>  > you need to move to SQL Server.
>
> If you wasn't too drunk or too dumb to read, you'd know he's already using a
> server database (doesn't have to be MS SQL Server, can use lots of them with
> ODBC).
>
>  Mr. Kowalski
 >> Stay informed about: multi-source odbc to single table