| Hi Tom,
This is what I did.
From the ODBC Administrator:
---------------------------
1. Defined a file dsn called TOM1 to attach to an Rdb 70 multifile
personnel database. (Server=dbs400, class=generic, user=sqluser70,
attach='attach filename mf_personnel').
2. Defined a user dsn called MF_PERSONNEL70 to attach to an Rdb 70
multifile database. (Server=dbs400, class=generic, user=sqluser70,
attach='attach filename mf_personnel').
From MS Access (I know you are using Excel but I don't have this
installed on my Win95 machine):
-----------------------------------------------------------------
3. Link to a table using TOM1 -
"Reserved error (-7778), there is no message for this error."
4. Link to a table using MF_PERSONNEL70. Success.
From notepad:
------------
5. Opened the file tom1 found in:
C:\Program Files\Common Files\ODBC\Data Sources. It looked like the following:
[ODBC]
DRIVER=Oracle ODBC Driver for Rdb
UID=sqluser70
DBA=W
DATABASE=attach 'filename mf_personnel'
CLS=generic
SVR=dbs400
6. Modified the above file to look like:
[ODBC]
DSN='mf_personnel70'
From MS Access:
--------------
7. Link to a table using TOM1. Success.
NOTE: This would not work until I deleted every single line from file
TOM1 with the exception of the line [ODBC]. Just putting in the
line DSN=etc. was not sufficient. Everything else had to be deleted.
I know this is a cumbersome workaround but I sure hope it works for you!
I've made a note to myself to update you should I hear of any plans to
make the oracle rdb odbc driver level 3 compliant.
Diane
|
| From: BROKE::BITHER "Please reply to dbither@us.oracle.com" 28-MAY-1997 17:05:27.20
To: MEMORMAN
CC: BITHER
Subj: New Stars Article
TITLE: Reserved Error (-7778), There is No Message for this Error
PRODUCT: Oracle Rdb ODBC
RELATED
PRODUCTS: Oracle Rdb
Microsoft 97 Products
OP/SYS: OpenVMS VAX, OpenVMS AXP
SOURCE: Oracle Worldwide Customer Support
PROBLEM:
Attaching to an Rdb database from a Microsoft 97 product results in
the following error:
"Reserved error (-7778), there is no message for this error."
PROBLEM CAUSE:
Starting with the Microsoft 97 products, Microsoft released a new ODBC
driver manager that allows the definition of file data source names (DSNs).
File DSNs require level 3 complicity. The Oracle Rdb Odbc driver is not
level 3 compliant and when used with file DSNs results in the above error.
The Oracle Rdb Odbc driver works with user DSNs which are level 2 compliant.
WORKAROUND:
Define a user DSN and modify the file DSN to point to the user DSN.
From the ODBC Administrator:
---------------------------
1. Define a file DSN called XXX to attach to an Rdb database.
2. Define a user DSN called ZZZ to attach to the same Rdb database.
Use the same parameter definitions as used to define the file DSN
(i.e. server, class, user, and attach string should have the same values
for both DSN types.)
From an MS 97 Product:
----------------------
3. Test the user DSN. Attach to a table using ZZZ. This should work.
If it doesn't, continue debugging until you get your user DSN to work.
From notepad or any editor:
--------------------------
4. Open the file XXX found in:
C:\Program Files\Common Files\ODBC\Data Sources. It will look like
the following:
[ODBC]
DRIVER=Oracle ODBC Driver for Rdb
UID=username
DBA=W
DATABASE=attach 'filename name_of_rdb_database'
CLS=generic
SVR=nodename
5. Modify file XXX so that it points to the user DSN. Delete all other
lines:
[ODBC]
DSN='YYY'
From an MS 97 Product:
----------------------
6. Attach to a database using the file DSN XXX. This will now work.
NOTE: This will not work unless every single pre-existing line in file
XXX with the exception of line [ODBC] is deleted. Just putting
in the line DSN=user_dsn is not sufficient.
SOLUTION:
There are no plans to make the Oracle Rdb Odbc driver level 3 compliant
at this time.
\
\ CONTRIBUTORS:
\
\ Technical: Diane Bither
|