Well, that took care of the issue with the "record has been changed" error
message. And, though the other error was intermittent so I can't directly
test it, I'm sure having the timestamp field will take care of that other
one, as well. Thanks again for your help!

Neil


"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:7qdbu0diucqfv72eove4jglip8u5cghrrj@4ax.com...
> There isn't anything odd that SQL Server does with new
> tables. This issue is more likely due to using ODBC or some
> Access specific configuration, setting.
> The "record has been changed" error you posted can happen
> with a few different scenarios with ODBC linked tables in
> Access. Basically, ODBC will use a timestamp to determine if
> the record has been updated. If there is no timestamp
> column, it compares all column values to see if the record
> has been updated.
> Some situations can cause Access to become "confused" as to
> whether the record has been updated - such as having float
> data types. Try adding a timestamp column to the SQL table
> and see if the fixes the problem. There should be some
> Access knowledge base articles on this subject that you may
> want to search for.
>
> -Sue
>
> On Wed, 12 Jan 2005 20:28:22 GMT, "Neil Ginsberg"
> <nrg@nrgconsult.com> wrote:
>
>>Another note on this issue. If I go into an existing record, type data in
>>a
>>field, save the record (using Shift+Enter), then immediately type more
>>data
>>in the same field, I get the message, "The data has been changed. Another
>>user edited this record and saved the changes before you attempted to save
>>your changes." Once the message is cleared, the steps of
>>typing/saving/typing can be performed without any errors. But when you
>>first
>>go to a record and perform those steps, the error always comes up.
>>
>>This happens both on the network version of the database, as well as in my
>>personal copy (using MSDE), so I know it's not a multi-user issue, but
>>some
>>kind of a glitch. It seems that it might be related to the below message
>>re.
>>losing data, so I posted it here.
>>
>>Any ideas?
>>
>>Thanks!
>>
>>Neil
>>
>>
>>"Neil Ginsberg" <nrg@nrgconsult.com> wrote in message
>>news:yefFd.5637$Ii4.2334@newsread3.news.pas.eart hlink.net...
>>> We're using SQL Server 7 with an Access 2000 MDB as a front end with
>>> ODBC
>>> linked tables. I recently created a new set of tables for the app, and
>>> users are complaining that unsaved data is being lost when they move to
>>> a
>>> new record. This seems to be the case when there are multiple users.
>>> When
>>> there is a single user using it, we don't seem to have that problem.
>>>
>>> It seems that we had this problem when we first converted from an MDB
>>> back
>>> end to a SQL 7 back end, years ago, but we haven't had this problem in a
>>> while. These are the first "entirely new" tables created in several
>>> years,
>>> and we seem to be having that problem again.
>>>
>>> Is this something with SQL 7 when it's dealing with new tables? Any
>>> ideas
>>> on what to do?
>>>
>>> Thanks!
>>>
>>> Neil
>>>
>>
>