By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,870 Members | 1,855 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,870 IT Pros & Developers. It's quick & easy.

Access 2002 mdb fails when used by Access 2002

P: n/a
We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.

Any help is appreciated.

Apr 19 '07 #1
Share this Question
Share on Google+
8 Replies


P: n/a
mainframetech wrote:
We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.

Any help is appreciated.
Is the query created in the query builder or via handcode? If handcode,
is it possible something is misspelled? An incorrect reference?

Since it's multi-file, perhaps send the user a set of that
queries...each query truncate/remove one table and column references to
that table. You might find which table it's bombing out on.

Maybe delete, then compact, then rewrite the query from scratch.
Apr 19 '07 #2

P: n/a
On Apr 19, 12:56 pm, salad <o...@vinegar.comwrote:
mainframetech wrote:
We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.
Any help is appreciated.

Is the query created in the query builder or via handcode? If handcode,
is it possible something is misspelled? An incorrect reference?

Since it's multi-file, perhaps send the user a set of that
queries...each query truncate/remove one table and column references to
that table. You might find which table it's bombing out on.

Maybe delete, then compact, then rewrite the query from scratch.
All the simple stuff has been checked into. The mdb with the
query is created on Access2000 and tested here and at the client
location on an Access2000 machine. This runs fine. When put on an
Access2002 machine at the client location, it fails with the logon/
password error (ORA-01017) almost immediately.

Chris

Apr 20 '07 #3

P: n/a
mainframetech wrote:
On Apr 19, 12:56 pm, salad <o...@vinegar.comwrote:
>>mainframetech wrote:
>>>We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.
>> Any help is appreciated.

Is the query created in the query builder or via handcode? If handcode,
is it possible something is misspelled? An incorrect reference?

Since it's multi-file, perhaps send the user a set of that
queries...each query truncate/remove one table and column references to
that table. You might find which table it's bombing out on.

Maybe delete, then compact, then rewrite the query from scratch.


All the simple stuff has been checked into. The mdb with the
query is created on Access2000 and tested here and at the client
location on an Access2000 machine. This runs fine. When put on an
Access2002 machine at the client location, it fails with the logon/
password error (ORA-01017) almost immediately.

Chris
I don't know your setup. Does the remote site have multiple users? If
so, is it only 1 user that has a problem? Is he/she the only person
using A2002? Does that person have A2000? Does it work on that machine
with A2000 but rejects A2002?

Again, since it's a multi-table query, can that person access each table
in a simple SQL Select?

I went to
http://groups.google.com/advanced_search?q=&
and entered
ora-01017 ora01017
in the With At Least One Word box and entered
*Oracle*
in the groups box and searched.

There's 271 messages you can browse, one of them may turn the lightbulb on.

Apr 21 '07 #4

P: n/a
On Apr 20, 9:27 pm, salad <o...@vinegar.comwrote:
mainframetech wrote:
On Apr 19, 12:56 pm, salad <o...@vinegar.comwrote:
>mainframetech wrote:
>>We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.
> Any help is appreciated.
>Is the query created in the query builder or via handcode? If handcode,
is it possible something is misspelled? An incorrect reference?
>Since it's multi-file, perhaps send the user a set of that
queries...each query truncate/remove one table and column references to
that table. You might find which table it's bombing out on.
>Maybe delete, then compact, then rewrite the query from scratch.
All the simple stuff has been checked into. The mdb with the
query is created on Access2000 and tested here and at the client
location on an Access2000 machine. This runs fine. When put on an
Access2002 machine at the client location, it fails with the logon/
password error (ORA-01017) almost immediately.
Chris

I don't know your setup. Does the remote site have multiple users? If
so, is it only 1 user that has a problem? Is he/she the only person
using A2002? Does that person have A2000? Does it work on that machine
with A2000 but rejects A2002?

Again, since it's a multi-table query, can that person access each table
in a simple SQL Select?

I went to
http://groups.google.com/advanced_search?q=&
and entered
ora-01017 ora01017
in the With At Least One Word box and entered
*Oracle*
in the groups box and searched.

There's 271 messages you can browse, one of them may turn the lightbulb on.- Hide quoted text -

- Show quoted text -
They have already tried accessing each table directly, which works
fine. We have tried it on other machines that have Access2000, and it
works fine. Only under Access2002 does it fail. the machine at the
client site has only one user. I've gone through the MS Knowledge
Base, but don't see anything there.

Chris

Apr 23 '07 #5

P: n/a
mainframetech wrote:
On Apr 20, 9:27 pm, salad <o...@vinegar.comwrote:
>>mainframetech wrote:
>>>On Apr 19, 12:56 pm, salad <o...@vinegar.comwrote:
>>>>mainframetech wrote:
>>>>>We are having a problem with Access 2002 as opposed to Access 2000.
>A multi-file query was set up under 2000 and tested good. Access is
>connected through a link to an Oracle 9.1 database. The database
>(mdb) was installed in
>remote client machines working with Access2000 and it worked fine.
>When the query was put on an Access2002 machine, it came up with
>"ORA-01017 invalid logon/password", and fails. The failing machine
>passes other queries and operations with the same Oracle database
>without problem.
>>>> Any help is appreciated.
>>>>Is the query created in the query builder or via handcode? If handcode,
is it possible something is misspelled? An incorrect reference?
>>>>Since it's multi-file, perhaps send the user a set of that
queries...each query truncate/remove one table and column references to
that table. You might find which table it's bombing out on.
>>>>Maybe delete, then compact, then rewrite the query from scratch.
>> All the simple stuff has been checked into. The mdb with the
query is created on Access2000 and tested here and at the client
location on an Access2000 machine. This runs fine. When put on an
Access2002 machine at the client location, it fails with the logon/
password error (ORA-01017) almost immediately.
>>>Chris

I don't know your setup. Does the remote site have multiple users? If
so, is it only 1 user that has a problem? Is he/she the only person
using A2002? Does that person have A2000? Does it work on that machine
with A2000 but rejects A2002?

Again, since it's a multi-table query, can that person access each table
in a simple SQL Select?

I went to
http://groups.google.com/advanced_search?q=&
and entered
ora-01017 ora01017
in the With At Least One Word box and entered
*Oracle*
in the groups box and searched.

There's 271 messages you can browse, one of them may turn the lightbulb on.- Hide quoted text -

- Show quoted text -


They have already tried accessing each table directly, which works
fine. We have tried it on other machines that have Access2000, and it
works fine. Only under Access2002 does it fail. the machine at the
client site has only one user. I've gone through the MS Knowledge
Base, but don't see anything there.

Chris
If none of the Google group messages had anything that pointed to an
solution then you might get a response in an Oracle forum.

Is it possible there is a driver incompatability? At this point I'm
clutching at straws. You too probably.

Apr 23 '07 #6

P: n/a
MDB isn't reliable
it is a TOY database

On Apr 19, 8:33 am, mainframetech <chough...@insidefsi.netwrote:
We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.

Any help is appreciated.

Apr 23 '07 #7

P: n/a
On Apr 23, 7:17 pm, "Susie DBA [MSFT]" <susie...@hotmail.comwrote:
MDB isn't reliable

it is a TOY database

On Apr 19, 8:33 am, mainframetech <chough...@insidefsi.netwrote:
We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.
Any help is appreciated.- Hide quoted text -

- Show quoted text -
Thanks Susie, but that's what I have, and that's what I need a
suggestion for.

Chris

Apr 24 '07 #8

P: n/a
On Apr 23, 7:17 pm, "Susie DBA [MSFT]" <susie...@hotmail.comwrote:
MDB isn't reliable

it is a TOY database

On Apr 19, 8:33 am, mainframetech <chough...@insidefsi.netwrote:
We are having a problem with Access 2002 as opposed to Access 2000.
A multi-file query was set up under 2000 and tested good. Access is
connected through a link to an Oracle 9.1 database. The database
(mdb) was installed in
remote client machines working with Access2000 and it worked fine.
When the query was put on an Access2002 machine, it came up with
"ORA-01017 invalid logon/password", and fails. The failing machine
passes other queries and operations with the same Oracle database
without problem.
Any help is appreciated.- Hide quoted text -

- Show quoted text -
Thanks for the help Susie. Access 2002 is what we have, and what we
have to debug.

Chris

Apr 25 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.