Hey! When linking external tables from ODBC databases in MS Access 2002, how do I get tables with SYS* prefixes?
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaraccess/html/msdn_odbcreg.asp notes exactly the reverse. How to tune ODBC so that an external application can see the Access system tables by editing the Windows registry (no need to do it, it's default).
Symmetry lets me assume you should edit the Oracle registry (or its equivalent) to allow visibility of system tables to an external ODBC program. It's unlikely indeed that the 'destination' could define what the 'source' makes available. But I must admit I never read the ODBC standard documents as defined by the SAG, so it's a guess indeed.
It may be necessary to define a view over the system tables in the source database, and use ODBC to access that view (if that's allowed).
Or, if all else fails, to copy them regularly to a 'normal' table, which you can surely access. But that's a rather nasty workaround.
Anyway, this is not an Access-problem. Access is only using a ODBC-datasource, which any Windows-program that knows how to connect to an ODBC-driver can do.
Hope this helps.
Kees
The tables I want to access is not really a ''system'' table. It just has a sys prefix in front, for example, sysadm.table_name. For some reason, it doesn't list these tables when showing the available tables for linking. Access thinks it must be a system table and it hides it. How do I unhide it?
Tools>Options>View and check 'View system objects'. That's for Access 97 at least. Other versions might be different. Check the help, if necessary.
Kees
| Forum legend: | |
| Locked thread | |
| Moderator | |
![]() |
CNET staff |
![]() |
Samsung staff |
| Norton Authorized Support team | |
| AVG staff | |
| Windows Outreach team | |
![]() |
Dell staff |
| Intel staff | |