Re: SQL Server / ADP Not Saving All Information
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Wed, 21 Feb 2007 03:00:04 -0500
When using Access, it's always better for each user to have its own
front-end. Albeit to a lesser degree, this remains true with ADP. Before
closing this path, you should give it a try.
SQL-Server has the opposite of the auto-save feature: in case of a
connection lost; it will roll back any uncommitted transaction; even if this
transaction has been partially or entirely written. However, Access use
simple transaction, with the minimum number of operation per transaction; so
this shouldn't be a problem for you.
You don't say if you are losing data only when you completely lose the
connection, including the remote desktop, so I cannot tell you more on this.
You should also say if you are doing the editing of the data with your own
VBA code or if you are using exclusively bound forms to do this.
Finally, it's hard for me to believe that you can lose the remote destkop.
I would have thought that a setting can control this and keep any desktop
open when a connection goes down: the ADP application should be kept running
when you re-login on TS.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"virginia via AccessMonster.com" <u19512@uwe> wrote in message
news:6e1a7495c26e9@xxxxxx
Currently my company has outsourced IT and we have to access all of our
information via a Remote Desktop. I have an Access Frontend (2003) and a
SQL
Server (2000) backend running on Windows 2003 Terminal Server. The problem
is
that the SQL Server is not always saving information and our Outsourced IT
has come up with different options, first saying it was the Access 2003
Front-
end replicating, which it is not replicating. I have one read-only file
for
all users to access and 2 other front-ends for modification. I am the only
one that modifies anything, but there is one other person that inputs and
deletes, all other users are read-only. I didn't see the need for each
user
to have their own front-end, they access it in one central location. So,
that
ended that discussion.
The next option they had was that we needed to put a Exclusive Lock on SQL
Server to update and delete, but from what I have read, this shouldn't be
the
case either. I have researched and went to various sites about locks and
the
Server automatically gives you a lock when you are updating and deleting.
We have a choppy connection at times and if the connection is lost, would
that cause the data not to save? At times, we completely loose the
connection
and the remote desktop. Does SQL Server 2000 have an autosave feature? Any
thoughts would be appreciated.
--
Message posted via http://www.accessmonster.com
.
- Follow-Ups:
- Re: SQL Server / ADP Not Saving All Information
- From: virginia via AccessMonster.com
- Re: SQL Server / ADP Not Saving All Information
- References:
- SQL Server / ADP Not Saving All Information
- From: virginia via AccessMonster.com
- SQL Server / ADP Not Saving All Information
- Prev by Date: Re: Vista + Access2007 + SQLExpress ADP
- Next by Date: Re: SQL Server / ADP Not Saving All Information
- Previous by thread: SQL Server / ADP Not Saving All Information
- Next by thread: Re: SQL Server / ADP Not Saving All Information
- Index(es):
Relevant Pages
|
Loading