Data Changed (I know, a million people have talked about it)

  • Thread starter Thread starter Dave Corun
  • Start date Start date
D

Dave Corun

I've searched Google's archive of this group, and tried the following
things, to no avail. Everytime a form comes up that displays data we get
the "Data Changed by Another User, Copy to Clipboard | Drop Changes".

The background:
* SQL Server 2000 backend, Access 2000 frontend. The Access 2000 backend
was recently upsized to SQL Server 2000.

* My bit fields don't allow Nulls, and have default values of zero. There
are no records anywhere in the system that have a Null value in a bit field.
* Tried changing my bit fields to tinyint.
* Created a new Access database and imported all of the tables, forms, etc.
* Created a relationship in the Access front end, as well as the SQL Server
database.
* Verified that the SQL Server tables have PKs and correct relationships.
* Added timestamps to all my tables, and deleted and relinked those tables
to my Access frontend.
* Installed the latest MDAC (2.8) and Windows 2000 Service Pack 4
* Installed SQL Server Service Pack 2.
* Installed Office 2000 Service Pack 3.
* Checked the network cards against the HCL list, and they're good...
* Watched the hubs and switches for collisions, which there were few.

What am I missing? My client is very upset at this, and it's making my
small programming firm look very bad.

Amy more ideas?

// Dave
 
Do you have any code running behind the form that might be accessing the
recordset?

What happens if you open the table the form is based on directly?
 
As an aside, I suggest you also deploy SQL-Server SP3 which will protect you
against a very natsy worm.

Now to the problem, set row level locking on if it isn't already done. Most
of the time that I've seen this problem the "other user" is you opening a
second form on the same data. If that is your problem, the solution is to
open the first form as read-only so that it doen't lock the data.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
Options, advanced . . .
Dave Corun said:
Wait, how do I set row level locking? That might be the heart of it!

Thanks!

// Dave


As an aside, I suggest you also deploy SQL-Server SP3 which will protect you
against a very natsy worm.

Now to the problem, set row level locking on if it isn't already done. Most
of the time that I've seen this problem the "other user" is you opening a
second form on the same data. If that is your problem, the solution is to
open the first form as read-only so that it doen't lock the data.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
Click to expand...
 
Oh yeah, thats checked for everyone.

Any more ideas?

Thanks!

// Dave



Options, advanced . . .
 
Dude, I am so stuck right now. Please give me something else to try to
get rid of these Data Changed errors. My client is furious at me!



Thanks!!

// Dave




I've searched Google's archive of this group, and tried the following
things, to no avail. Everytime a form comes up that displays data we get
the "Data Changed by Another User, Copy to Clipboard | Drop Changes".

The background:
* SQL Server 2000 backend, Access 2000 frontend. The Access 2000 backend
was recently upsized to SQL Server 2000.

* My bit fields don't allow Nulls, and have default values of zero. There
are no records anywhere in the system that have a Null value in a bit field.
* Tried changing my bit fields to tinyint.
* Created a new Access database and imported all of the tables, forms, etc.
* Created a relationship in the Access front end, as well as the SQL Server
database.
* Verified that the SQL Server tables have PKs and correct relationships.
* Added timestamps to all my tables, and deleted and relinked those tables
to my Access frontend.
* Installed the latest MDAC (2.8) and Windows 2000 Service Pack 4
* Installed SQL Server Service Pack 2.
* Installed Office 2000 Service Pack 3.
* Checked the network cards against the HCL list, and they're good...
* Watched the hubs and switches for collisions, which there were few.

What am I missing? My client is very upset at this, and it's making my
small programming firm look very bad.

Amy more ideas?

// Dave
 
Back
Top