Strange (#Deleted) appearing in table

[Steven547]

Hope everyone had a good July 4th!

My issue is this: When I open a table in MS Access(linked table), all the data looks fine. However, when I create a query with that table, and enter criteria to search for, my results show up as (#DELETED)??

I'm lost as to why that is happening. Any ideas?

 

[Steven547]

Ok...seems like it might be a MS Jet 4.0 issue...Guess I have to have IT install the fix...hopefully that works unless someone knows of some other issue it might be...

 

[kjv1611]

Post back to let us know if the patch you're getting done works out. Either way, it'd be good to know - so we can help troubleshoot if it doesn't work; or if it does work, we'll have a little more info to assist others in troubleshooting their issues.

--

"If to err is human, then I must be some kind of human!" -Me

 

[PHV]

Does JetSQL recognize the PrimaryKey of your linked table ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[Steven547]

I'm waiting on our IT department to get back to me. Upon research on the net and Microsoft, I found this:

Microsofts Web Site: "Obtain the latest Microsoft Jet 4.0 service pack that contains an updated version of the Microsoft Jet 4.0 database engine.

For additional information about how to obtain the latest version of the Jet 4.0 database engine, click the following article number to view the article in the Microsoft Knowledge Base:
239114 (

http://support.microsoft.com/kb/239114/

) How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine
Back to the top
STATUS

This is a known issue in Microsoft Jet version 4.0.2927.4 and earlier. "

So, hopefully i'll find out for sure soon and I'll let everyone here know as well.

 

[PHV]

You still didn't answer my question ...

 

[Steven547]

Does JetSQL recognize the PrimaryKey of your linked table ? "

How would I find this out?

The primary key is what is displaying the #DELETE.

 

[PHV]

How would I find this out?
Open the linked table in design view.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[ccv]

If you're linked to an oracle table read this:

http://support.microsoft.com/kb/248186

 

[Steven547]

Thanks. I'll have to look into that as well. We are running Access 2003, but we are linking to an Oracle Driver (Microsoft ODBC for Oracle).

When I apply a "Group By", that error disappears. So, more research!