when user leave's the application for while connection to server stops
and data shown in form is #deleted
how to prevent it?

sam

You didn't indicate what application you are using or how
you are accessing the SQL Server data.
But it can be caused by several things - generally related
to indexing - such as using a float as the index or as part
of the index or having nulls as values in part of the index.
There were similar to this when using Bigints with some apps
which wouldn't map the data type correctly. That's generally
fixed in service packs by now depending on what you are
using. If you are using Access, make sure you have the
latest Jet service pack.
ODBC is key-set driven and fetches are generally done in two
steps based upon the unique index of the table where first
it grabs the index and then it goes back, looks for the
index and gets the rest of the row based on the index. If
it can't find the index or gets 'confused' on the index in
the second step (floats can confuse it as floats are
approximate data types), it will assume the record has been
deleted.

-Sue

On Mon, 12 Dec 2005 12:33:35 +0200, "Sam"
<focus10@zahav.net.il> wrote:

>when user leave's the application for while connection to server stops
>and data shown in form is #deleted
>how to prevent it?
>
>sam
>

In addition to Sue's comments, if you are using Access, you should add a
timestamp field to all of your Access linked tables. Access uses the
timestamp field to determine if the data has changed since it was last
fetched.

"Sam" <focus10@zahav.net.il> wrote in message
news:O2mNQew$FHA.2036@TK2MSFTNGP14.phx.gbl...
> when user leave's the application for while connection to server stops
> and data shown in form is #deleted
> how to prevent it?
>
> sam
>
>