We guesstimate that its because someone else deletes data in the table
while you have it open. I have not tested the guesstimate.
CC
"Sorge, Bruce" <[EMAIL PROTECTED]>@dfwcfug.org on 01/11/2001 03:18:40
PM
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Database question
As luck would have it we are running SP4 on the SQL Server. So I am back
at square one. Once again, if there is anyone out there that has run into
this issue or they have access to their DBA, any information would be
greatly appreciated.
-----Original Message-----
From: Jeremy Ridout [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:54 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Database question
We have SQL Server 7.0. If they fixed it in a 6.5 service pack, they
unfixed it with SQL 7.0.
-----Original Message-----
From: Sorge, Bruce [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:53 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Database question
After further investigation I have discovered that this is a known bug in
SQL Server 6.5 and that SP3 for SQL Server (Not the NT Server OS) will fix
it. We are checking it out now to see if this is the case (if we are not
running Sp 3).
-----Original Message-----
From: Jeremy Ridout [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:49 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Database question
I see it everyday. I've given up on finding the answer of WHY this
happens. But I think that it has something to do with Access not
maintaining its "session" with SQL Server (or vice versa).
When you leave the datasheet table view on your screen and the connection
times out, Access, which wants to continually update the view, can't
restore the connection and assumes the data is deleted. The fix, close
your table datasheet view and reopen. It will reconnect and populate the
window properly.
There must be a setting for it somewhere. We have a single mdb with links
to the SQL tables. One other person in my department and I both open the
same file from a shared drive. I never see the #deleted error on my
computer and she sees it constantly. (Then again, I don't leave my
datasheet views open and she does).
Jeremy
-----Original Message-----
From: Sorge, Bruce [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:37 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Database question
Well, actually the answer I got was not the answer that I was looking for.
Microsquash says that The #Deleted error value means that the record being
referred to has been deleted. In a perfect world I suppose that this would
be true. However, the the real NON Microsquash world this is not the case.
The information is there and the records have NOT been deleted. So now I
am back at square one. If anyone out there has seen or heard of this issue
I would LOVE to hear what you found out.
Thanks,
Bruce
-----Original Message-----
From: Jeremy Ridout [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:33 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Database question
What did you find out?
-----Original Message-----
From: Sorge, Bruce [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 11, 2001 2:32 PM
To: List (E-mail)
Subject: Database question
Never mind, I found the answer.
Bruce Sorge
Portal Services
Baylor Health Care Systems
Phone: 214-820-3142
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org
