| Title: | DEC ODBC Driver |
| Notice: | DEC ODBC Driver V2.0 Now Available |
| Moderator: | SQLSRV::MAVRIS |
| Created: | Tue Dec 29 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1357 |
| Total number of notes: | 4864 |
ODBC V2.10.11 One of our customer have been attempting to use Microsoft Access 2.00 to access a VAX RDB VIEW using an Oracle ODBC Driver. User can browse the data in table view and extract based upon various selection criteria. However, user have been unable to link a MSAccess table to a field in the view with is indexed in the underlying table. When user do so the PC simply hangs. Their DBA for the VAX has checked the view and it performs properly when using SQL on the VAX. It is essential that customer can access a view as in this instance it is being used to mask certain fields in the underlying table. Did anyone came across with the same problem? It seems to be MSAccess cannot properly access data in the RDB VIEW? Is there a workaround or a fix for this problem? Thanks, Michael.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1310.1 | views work fine for me | M5::JBALOGH | Fri Mar 07 1997 11:10 | 17 | |
The only problem I have heard of with ODBC and views was back around
1.1 ODBC and was fixed in 1.1-A. MS Access should be able to get to RDB
views just fine.
The view will NOT expose any indexes on underlying tables though. You
will not be able to update through the view with MS Access and you will
not be able to link via primary keys on underlying tables since these
keys and indexes are not exposed through the driver...
You need to chase this down further. Look at some driver and client
logs to see exactly what it is doing. Look at the SQLSRV execution
process to see what it is doing. They may also want to upgrade to a
newer version of MS Access as 2.0 is getting pretty old and I doubt
Microsoft will support it. Also, make sure you are on current versions
of ODBC and SQLSRV...
John
| |||||