April 24, 2006 at 5:47 pm
Hi there.
I have SQL Server tables linked through ODBC.
"Sometimes" when I open tables the data fields display "#Deleted". Sometimes not.
Either way the data is there.
If I run a make table query, the data copies down intact.
Does anyone have an idea why those "#Deleted" placeholders are displayed.
Is it a permission issue?
I use 'sa' when I log in.
Thanks.
April 25, 2006 at 2:10 am
I've seen this before when a change has been made to the data but the screen has not refreshed, when you refresh the dataset the data is shown cleanly. It is not a permissions issue.
If you open a linked table whilst updates are being made to the records, especially if the update is a drop and recreate, I expect this might be the result.
Regards
Carolyn
April 25, 2006 at 2:10 am
I've seen this before when a change has been made to the data but the screen has not refreshed, when you refresh the dataset the data is shown cleanly. It is not a permissions issue.
If you open a linked table whilst updates are being made to the records, especially if the update is a drop and recreate, I expect this might be the result.
Regards
Carolyn
April 25, 2006 at 9:30 am
I found this at microsoft, but I'm certain that there's another, more common, circumstance under which this can occur. If I find it, I'll post it here.
Meanwhile...
http://support.microsoft.com/default.aspx?scid=kb;en-us;269444
April 25, 2006 at 5:50 pm
Hi there,
Unsure if you have the problem solved yet. I had this before, and I found out that most of the time, it is the data itself that causes this. Some of the data type in SQLServer aren't intepret well in Access.
For example, if you have a bit type column, ensure that all data have default value of 1 or 0. The bit data type will be interpret as Yes/No field in Access, Access Yes/No data type only accept Yes or No, it cannot accept NULL. Therefore, if you have a null value in the bit fields, Acccess cannot interpret that.
Another case was simply the data not clean.
If you have lots of data in that table, then maybe create a view to filter some columns, data from the table and link it to Access for trouble shooting.
Hope that helps.
regards,
PL
April 26, 2006 at 7:20 am
It is likely that the table you have linked to does not have a primary key. The best way I can think what Access is doing, is that Access cannot accurately refer to the unique specific record in the row, so it "thinks" the row is deleted.
Hope this helps
Mark
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply