Re: Linked Tables in Access
- From: "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 16:43:45 -0800
Hi, Declan.
action queries
written in Access are run with Access specific functions and references to
controls on Access forms, is the processing done on the Server or the Client?
If you're using Access built-in functions in your queries, then you're using the
Jet Expression Service, which means you're doing the processing on the client,
not the server, because only Jet can access the Jet Expression Service, but SQL
Server and other database engines can't. If you want the processing to be done
on the server, use SQL passthrough queries, which would require T-SQL syntax.
Of course, T-SQL doesn't recognize VBA, so you'd have to use built-in T-SQL
functions or create your own custom T-SQL functions.
Do you still run the risk of corrupting the "back-end" database if a write
operation is interrupted if you use tables in SQL Server database as linked
tables instead of using tables in an Access database as linked tables?
Even SQL Server database files can become corrupted, but the risk is far lower
that this will be a problem with linked SQL Server tables than when storing the
data in Jet tables. The reason for this is that if a write operation is
interrupted in a client/server database engine such as SQL Server, the failed
transaction will be rolled back so that the data remains in a consistent state.
Jet doesn't use transactions, so failed transactions can't be rolled back.
For example, if a debit of $200 were made from your savings account and a $200
credit were made to your checking account (which is what happens when you
"transfer" money from savings to checking), and the power failed after the debit
but before the credit to your checking account, Jet would "lose" $200 from your
savings account. If the same power failure happened in SQL Server, the $200
debit from savings would be rolled back when the database was recovered, as if
no transaction had occurred.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.
"Declan" <Declan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9712B4F5-D0DF-47F0-B684-FC22576C9E88@xxxxxxxxxxxxxxxx
If SQL Server tables contained on a Server computer are used as linked tables
in an Access database on a client computer via ODBC, and action queries
written in Access are run with Access specific functions and references to
controls on Access forms, is the processing done on the Server or the Client?
Do you still run the risk of corrupting the "back-end" database if a write
operation is interrupted if you use tables in SQL Server database as linked
tables instead of using tables in an Access database as linked tables?
.
- Follow-Ups:
- Re: Linked Tables in Access
- From: Declan
- Re: Linked Tables in Access
- Prev by Date: auto populate field
- Next by Date: Re: auto populate field
- Previous by thread: auto populate field
- Next by thread: Re: Linked Tables in Access
- Index(es):
Relevant Pages
|
Loading