[AccessD] ODBC

Hi Stuart,

Do you have experience with Terminal Server with multiple users running
separate front ends to a common Access data file?  I would love to pick
your brain if you do - or anyone else for that matter.  I currently have
a new IT guy who is in conflict with the old IT guy about our use of
Terminal Server.  We are having data corruption and the new guy says it
is because of Terminal Server - too many connections to the back end
from the same box.  I know very little about the
network/hardware/software aspects and am at a loss.  I have made no
changes to the database, yet in the past two weeks we have experienced
several "corruptions", when the database had been stable for nearly a
year without a corruption.

Any help would be appreciated.

Jennifer

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
McLachlan
Sent: Friday, October 06, 2006 8:05 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] ODBC


On 6 Oct 2006 at 19:09, Jennifer Gross wrote:

> Question 1:  When an Access front end connects to an Access backend is

> it an ODBC connection?

No, it's a JET connection, which is more efficient than ODBC

> Question 2:  If multiple users have separate front ends on the same 
> Terminal Server box linking to a back end on a different box, are they

> opening separate connections to the back end (ODBC or otherwise), or 
> are they sharing the same connection?

They are separate connections.

-- 
Stuart


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com