odbc呼叫失败 [英] odbc call failed

问题描述

我使用vb 6和postgresql作为后端。当在vb中运行该函数时，它显示odbc调用失败的错误消息。但是当我在postgresql中运行相同的功能时，它很容易运行。任何人都可以建议我如何增加odbc中的执行时间，因为数据库太大了，

解决方案

这里没有足够的信息来理解其性质你的问题。

请在你的代码中发布相关的摘录及其生成的错误信息。

我正在使用的功能

展开 | 选择 | Wrap | 行号

我既不使用VB也不使用ODBC，而是谷歌搜索运行时错误'3146''，odbc调用失败"

返回了不少引用。

看来这个问题可能与你的ODBC驱动有关，你检查一下是否有更新的版本？

我看到的其他一些案例与查询没有返回受影响的行数有关，显然司机期待这个。


我会考虑这些步骤：


1.我认为你担心由于长时间运行的查询导致的性能和可能的超时错误。

创建一些类似于你的测试功能，但确保它做的很少并运行快速。

看看你是否可以从你的应用程序执行它。


2.修改此函数以返回一些受影响的行，可能是一些虚拟整数。


3.制作你的应用程序而不是功能。运行执行类似操作的SQL查询，看看会发生什么。


4.检查您正在使用的ODBC驱动程序的更新，或者可能完全找到不同的驱动程序。


5.花一些时间在网上搜索


以下是几个可能相关的链接。

http://www.pcreview.co.uk/forums/thread-1865044。 php
http：/ /www.vbforums.com/archive/index.php/t-338252.html

i am using vb 6 and postgresql as the back end. when running the function in the vb , it shows the error message of odbc call failed. but when i run the same function in the postgresql then it runs easily. can anyone suggest how can i increase the execution time in the odbc since the database is too huge,

解决方案

There''s not enough information here to understand the nature of your problem.
Please post the relevant excerpt from your code and the error message it generates.

i am using the function

Expand|Select|Wrap|Line Numbers

I don''t use neither VB or ODBC, but a Google searh on "run time error ''3146'', odbc call failed"
returned quite a few references.
It appears this problem may be related to your ODBC driver, did you check if a newer version is available?
Some other cases I saw were related to query not returning the number of rows affected, apparently the driver was expecting this.

I would consider these steps:

1. I think you were concerned with performance and possible timeout error due to the long running query.
Create some test function similar to yours, but make sure it does little and runs fast.
See if you can execute it from your app.

2. Modify this function to return a number of affected rows, perhaps some dummy integer.

3. Instead of the function, make your app. to run SQL query performing a similar operation, see what happens.

4. Check for updates on the ODBC driver you are using, or maybe find a different driver altogether.

5. Spend some time searching net with Google

Here are couple links that could be relevant.

http://www.pcreview.co.uk/forums/thread-1865044.php
http://www.vbforums.com/archive/index.php/t-338252.html

这篇关于odbc呼叫失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！