odbc connection vs. linking

[Miskacee]

I have a database that whose tables are located in one Missouriand the front
end it located in Minn.. How do I connect the front in in Minn. with the
tables in Missouri? I use link locally but wanted to type in the path name
of the server in Missouri. Or should I connect though ODBC connection to the
tables?

Thank You!

 

[Douglas J. Steele]

To be honest, you shouldn't even consider using Access across a WAN.

 

[Miskacee]

I have no choice.

To be honest, you shouldn't even consider using Access across a WAN.

 

[Douglas J. Steele]

Using Access across a WAN is a disaster waiting to happen. You're almost
guaranteed to corrupt your back-end.

You might want to read what Albert Kallal has to say about using Access over
the WAN at http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

 

[Tony Toews [MVP]]

I have no choice.

Then resign your job. Using Access for the data storage on a LAN
won't work.

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/

 

[Sam Smith]

I have no choice.

Yes you do. You can use SQLServer 2005 Express - it's free and far less open
to corruption than Access is on it's own.

 

[Sam Smith]

----- Original Message -----
From: "Tony Toews [MVP]" <[email protected]>
Newsgroups: microsoft.public.access.setupconfig
Sent: Friday, May 18, 2007 5:29 AM
Subject: Re: odbc connection vs. linking

Then resign your job. Using Access for the data storage on a LAN
won't work.

Err - don't you mean WAN?

 

[Tony Toews [MVP]]

Then resign your job. Using Access for the data storage on a LAN
won't work.

GAK!!! I mean WAN, WAN not LAN. Sorry about that.

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/

 

[Tony Toews [MVP]]

Err - don't you mean WAN?

Absolutely.

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/

 

[Tony Toews [MVP]]

Yes you do. You can use SQLServer 2005 Express - it's free and far less open
to corruption than Access is on it's own.

Good idea. However the poster might not be able to install it.

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/

 

[David W. Fenton]

I have a database that whose tables are located in one Missouriand
the front end it located in Minn.. How do I connect the front in
in Minn. with the tables in Missouri? I use link locally but
wanted to type in the path name of the server in Missouri. Or
should I connect though ODBC connection to the tables?

You can't use ODBC from Access to connect to Jet data. It is simply
not allowed by Access.

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

['69 Camaro]

Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

I woudln't bother with Terminal Services at all

you should just use SQL Server and ADP and then you wouldn't have to spend
a fortone on terminal services licensing

 

[Tom Wickerath]

CORREECTION

I use Access across a WAN all the time

but I use a real-mans flavor of Access-- it is called Access Data Projects

MDB doesn't work across ANY networks; I mean these kids are dumb enough to
reccomend terminal server?

ROFL

move to ADP, kid

 

[Tom Wickerath]

doug

oh, so now it's not a performance thing-- it's a reliability thing

when are you dipshits goig to stop blaming the network and start blaming the
database?

I can use ADP across a WAN _QUITE_ nicely

 

[Tom Wickerath]

using Access for data storage on a LAN won't work?

so Tony is finally admitting defeat??

 

[Tom Wickerath]

the poster might not be able to install it?

do you really think that there is an IT department in the world that
wouldn't encourage a spoon-fed Access developer to grow into SQL Server?

Seriously guys-- come on

 

[Tom Wickerath]

I woudln't bother with Terminal Services at all

you should just use SQL Server and ADP and then you wouldn't have to spend a
fortone on terminal services licensing