Neil Ginsberg wrote:
> 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?

Try putting a timestamp column onto the new SQL tables, then re-attach.
Your existing tables probably already had them (created by upsizing wizard).

--
This sig left intentionally blank