SQL Server / ADP Not Saving All Information

[virginia via AccessMonster.com]

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.

 

[Sylvain Lafontaine]

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.

 

[aaron.kempf]

you've proabbly got a problem in your where clause.

or you're inserting records into a view and the records you insert to
not meet the criteria for your view so they're not showing up.

I would reccomend not outsourcing shit to india

there are plenty of people stateside that use Access quite well


btw; are you even using ADP?

if you're using MDB / MDE then you can just **** yourself

 

[virginia via AccessMonster.com]

I should have explained a little better. We have a TS with a drive that is
Read-only except to myself and one other person, so when individuals go into
the ADP they are read-only, so I didn't see a need to have each person with
their own ADP for viewing only. There are only 2 people that can make changes
and have a copy of their own ADP. Our connection, at times is choppy, and we
do completely loose connection and don't always get our Remote Session back.
Our Remote Server company is saying that the loss of the session is not
causing data loss, they seem to think that the Jet is being locked by users
when they enter the database. This is not an every time situation for the
data loss, it only seems to happen if we have a choppy connection or a
complete loss of connection. We enter our data into a Form that is bound. I
really appreciate all of your help and thank you for being so nice with your
answers.

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.

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

[quoted text clipped - 26 lines]

and the remote desktop. Does SQL Server 2000 have an autosave feature? Any
thoughts would be appreciated.

 

[Norman Yuan]

I should have explained a little better. We have a TS with a drive that is
Read-only except to myself and one other person, so when individuals go
into
the ADP they are read-only, so I didn't see a need to have each person
with
their own ADP for viewing only. There are only 2 people that can make
changes
and have a copy of their own ADP.

Still, each user get his own copy of Access front ent, be it *.mdb, or *adp,
is better than many use shares one file copy. However, this is not likely
the reason of data loss.

Our connection, at times is choppy, and we
do completely loose connection and don't always get our Remote Session
back.
Our Remote Server company is saying that the loss of the session is not
causing data loss,

They are probably correct on this. When your user lose the connection to the
Terminal Server, he just lose the image of what is running on the server and
the capability to interact with the remote desktop via the image, howeer the
remote session on the server is still there, that is, the ADP is still
running on the server, but you do not see it, thus, no data loss. Unless the
user session in server is terminated upon the loss of connection from user
end, that may force ADP to terminate, while the ADP is desinged such that
some data needs to be saved manually (for example, you used many unbound
forms with disconnected recordset...).

You may need to ask your TS provider to investigate further on the server
end to see what could happen when a connection to remote user is lost.

they seem to think that the Jet is being locked by users

Jet? Why Jet has something to do with ADP? Do they know what ADP is?

when they enter the database. This is not an every time situation for the
data loss, it only seems to happen if we have a choppy connection or a
complete loss of connection. We enter our data into a Form that is bound.
I
really appreciate all of your help and thank you for being so nice with
your
answers.

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.

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

[quoted text clipped - 26 lines]

and the remote desktop. Does SQL Server 2000 have an autosave feature?
Any
thoughts would be appreciated.