Error - Record has been changed by another user

I apologize in advance if this has been posted but if you get the attached error "The record has been changed by another user...", we've discovered that this error can occur if you have a SQL Server Data Type of "Float" and also a "Text" Data Type in the same table. We discovered that it only happens on some records though and I am not sure why this is so. The solution is apparently to add a TimeStamp Data Type to the SQL Server table which does seem to fix the problem. If anyone has any insight on any other solutions (we cannot change the Data Types) or the reasoning behind this error, I would greatly appreciate the feedback.Where exactly does the error come from. I assume the Access Side?|||Yes, it's from the Access side (and on the linked table itself) and I'm assuming it might have something to do with ODBC and when the record is updated somehow but I haven't been able to pinpoint any rhyme or reason. The frustating part is that there is no consistency on when it happens (i.e. every time the floating number is XXXX or has XXXX number after the decimal, or the record is edited, etc.)

I do know though that (in the case on 1 of the tables I have this problem on) that I can 0 out the floating number and the Text field will then work ok and (on this table) it's has -99.23443 numbers (from a geocoding process) in the floating field, but again, no rhyme or reason or on any specific number. It just randomly occurs on certain records (about 2 dozen on 2000 records).

No problem though editing the Text field in SQL Server itself.

Like I mentioned, the timestamp field in SQL Server seems to be the solution but I had one of our consultants investigate it thoroughly on the web and make some calls to Microsoft and he was unable to come up with any reasoning behind it.|||I'm assuming that this is an mdb and not an access data project.

Try and minic the problem with an adp...betcha it doesn't happen.

Linked tables are a pain...do you open all of the records to a table, or do you allow them to be selected by criteria...

I would recommend unbound everything|||Bound verses unbound doesn't matter (even though we use unbound). Neither does opening all the records verses opening just that record. Yes it is an mdb and you're probably right in that it wouldn't happen on an ADP but at this time that's not an option.

My guess is that it's something with ODBC but no one's been able to answer yet on why this occurs.

In regards to linked tables though, we've had great success in utilizing linked tables and haven't found them to be a pain. It gives us the flexibility of utilizing Access queries with code (and have users which like to create their own queries) which is something that couldn't be done not using linked tables. But optimally, not using linked tables would be nice but again, not an option for us.