ODBC Oddities

  • Thread starter Thread starter DOYLE60
  • Start date Start date
D

DOYLE60

I have a main frame computer which I grab data from using ODBC. When I link to
this one file, it gives me the word #Deleted in all the fields across for many
records. When I do the same in Excel, these records are not deleted and are
correct.

Why is Access not getting what Excel is getting through ODBC?

When I import the file into Access, as opposed to linking, the data also comes
in just fine.

Why is Access not linking what it obviously can import?

The records that are not coming in do have something in common. But nothing
that is odd or should be troublesome. They simply have one character and two
blanks in a certain field, where the other fields have two characters and one
blank or three characters and no blanks. Also, they have data in other fields
where the ones coming in do not have data.

I'm just working with a table, so no filters or queries are working on this
data.

This ODBC call used to work too? Whose problem is it? Access's? or my
mainframe company?

Any clues?

Matt
 
(e-mail address removed) (DOYLE60) wrote in
I have a main frame computer which I grab data from using ODBC. When
I link to this one file, it gives me the word #Deleted in all the
fields across for many records.
Click to expand...

There could be several reasons for this depending on version of Access,
type of backend, table design etc. Try searching for the #deleted keyword
in Access section at support.microsoft.com.

-- Dev
 
I have a main frame computer which I grab data from using ODBC. When
There could be several reasons for this depending on version of Access,
type of backend, table design etc. Try searching for the #deleted keyword
in Access section at support.microsoft.com.
Click to expand...

I read "Microsoft Knowledge Base Article - 128809" but don't understand the
resolutions. Are they all things to fix on the main frame and not in Access?

Matt
 
(e-mail address removed) (DOYLE60) wrote in
I read "Microsoft Knowledge Base Article - 128809" but don't
understand the resolutions. Are they all things to fix on the main
frame and not in Access?
Click to expand...

Note that the KB article applies to Access 97 and prior versions. It does
not state if newer Jet versions show the same problem.

That said, the items listed in the article are not really fixes but more of
a trouble-shooting list in your particular instance.

If the data is being imported without a problem (and the right columns are
marked as primary key(s)), then it could be an issue with the ODBC drivers
as well. Did you update any drivers as you stated in your original post
that the odbc call used to work. If it's not an updated driver then this
could prove tough to track down.

Try searching groups.google.com for possible solution. Also, as the Table
view is a dynamic view different from Importing or viewing it in Excel, see
if you get the same problem in a form based on the table or not.

-- Dev
 
Back
Top