oracle odbc 连接未获取所有列
我在访问 Oracle 10 企业服务器时设置了一个链接表。它在我的电脑上运行得很好。但我试图让一位同事设置相同的功能，但由于某种原因，她看不到表中的所有列。它连接，刷新，说它已链接，但并非所有列都在那里。在命令行上使用不同的客户端或 sql，我们可以看到整个表。只是不在 Access 中。唯一的区别是我使用的是 Oracle 9g Client，而她使用的是 Oracle 10g Express。有什么想法吗？
I have a linked table set up in Access to an Oracle 10 enterprise server. It works great on my computer. But I'm trying to get a co-worker set up with the same functionality, and for some reason, she can't see all the columns in the table. It connects, refreshes, says it's linked, but not all the columns are there. Using a different client or sql on command line we can see the whole table. Just not in Access. The only difference is that I'm using Oracle 9g Client and she's using Oracle 10g Express. Any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看看 HansUp 关于缓存的说法。我想指出一点。确保您的同事从相同的架构和相同的表中进行选择。多个模式（用户）可以具有相似的表名。
示例：
用户 a 有包含 x、y、z 列的表 x
用户 b 有包含 x、y 列的表 x
如果您以用户 a 身份登录并从 x 中选择 *，则您将收到的列是 x、y、z，
如果您以用户 b 身份登录并 select * from x 那么您将收到的列是 x,y
确保您登录到正确的用户或在 select 中明确声明您想要的模式，即 select * from ax;
Look into what HansUp stated about caching. There is one point I'd like to make. Ensure your co-worker is selecting from the same schema and same table. Multiple schemas (users) can have similar table names.
Example:
User a has table x with columns x,y,z
user b has table x with columns x,y
If you log in as user a and select * from x then the columns you will receive is x,y,z
if you log in as user b and select * from x then the columns you will receive is x,y
Either ensure you are logging in to the correct user or explicitdly state the schema you want in the select i.e. select * from a.x;
获胜者是......一个超过 255 列的表！无论出于何种原因，我的查询所需的列在我第一次运行它时可用，并且在所有后续运行中可供我的计算机使用。对于我的同事来说，无论出于何种原因，我们需要的 2 个列被认为属于 255+ 类别。
解决方法是在 Access 中的链接表上使用传递查询。是的，我同意 - 表/视图中超过 255 列是可怕的设计。不是我的错，只是需要数据！
And the winner is... a table with more than 255 columns! For whatever reason, the columns that I needed for my query were available the first time I ran it, and were available to my machine in all subsequent runs. For my co-worker, for whatever reason, 2 of the columns we needed were considered in the 255+ category.
The work-around is to use a pass-through query on the linked table in Access. And yes, I agree - 255+ columns in a table/view is HORRID design. Not my fault, just need the data!!