From Oracle to Access

[Guest]

I've been running the same queries for quite a while on access that came from
an IBM heratage mainframe with no problem. Now the data is coming from a
different source (oracle) that outputs it in what it claims is an Excel .xls
spreadsheet. Once you save it, you can't manipulate it (change field
properties etc.) until you import it into access. Since this is coming from
Oracle, it outputs all text fields. Once in access I can change it the way
the old data was but when I run my old queries, the old stuff still comes up
but not the new data, it's been driving me crazy. This is so strange it has
me up nights. I tried dumping it into a comma delimited .cvs file and then
importing it but it still won't show up in my queries. Any ideas?

 

[Lynn Trapp]

Have you tried linking directly to the Oracle database from Access?

 

[John Vinson]

I've been running the same queries for quite a while on access that came from
an IBM heratage mainframe with no problem. Now the data is coming from a
different source (oracle) that outputs it in what it claims is an Excel .xls
spreadsheet. Once you save it, you can't manipulate it (change field
properties etc.) until you import it into access. Since this is coming from
Oracle, it outputs all text fields. Once in access I can change it the way
the old data was but when I run my old queries, the old stuff still comes up
but not the new data, it's been driving me crazy. This is so strange it has
me up nights. I tried dumping it into a comma delimited .cvs file and then
importing it but it still won't show up in my queries. Any ideas?

Are your queries referencing the imported tables, or are they using
ODBC links to Oracle?

John W. Vinson[MVP]

 

[Guest]

I linked it with ODBC oracle 8 but it's even worse, I have to go in and
change all the date fields that come in as text and it still does not
recognize the new stuff. The old numbers were 6 digit number text with the
numbers first. The new ones are 9 digit and the text comes first. Old =
0489yup new yup3939393.

 

[Guest]

I use the same old queries I've used for a long time, the data is added to
the table with a table merge every week. When you look at the table the only
thing you can notice is the length in the ID #. I don't use a primary key as
one ID# can have many relationships which cause dupes, there is nothing else
to key off of. The data base is older than dirt so I can't just have access
create one.