VoiceGuide IVR Software Main Page
Jump to content

Odbc Filemaker Error

Recommended Posts

Hi,

 

I am trying to use voiceguide with Filemaker through ODBC. But I am getting an error even for a simple select * from table statement:

 

This is the error that is preventing the connection to the database

ERROR: OpenRecordset: Execution cancelled.

 

Here is the tracelog and any help will be appreciated.

 

Thanks a lot,

 

AT

 

95875 5 tapie callstate OFFERING 65982 0 4

95875 5 Answer the call

95875 5 lineAnswer(65982) => 66153

95875 5 tapie linedevstate 2048 0 0

95875 5 tapie ring 1

95875 5 tapie callinfo MONITORMODES

96875 5 tapi Reply 66153 0

96890 5 tapie callstate CONNECTED 65982,16,0

96890 5 WorkingModeTAPI=

96890 5 WorkingModeScript=

96890 5 TimeoutClear

96890 5 [select Query] Playing

96890 5 [select Query] Playing (C:\Documents and Settings\Administrator\Desktop\VOICE\PRESS 1.wav)

96953 5 PlaySoundStart ok [C:\Documents and Settings\Administrator\Desktop\VOICE\PRESS 1.wav]

96953 5 TimeoutClear

96953 5 RunModule PLAY end

96953 5 wa(3812,99689000)

96953 5 tapie linedevstate 4 0 0

96953 5 tapie callinfo MONITORMODES

96953 5 tapie callinfo MONITORMODES

02218 5 Play End line[5] (id=996890)

02234 5 LsPlayMsg EV_PLAY_FINISHED

02234 5 TimeoutSet 10 EV_TIMEOUT_HANGUP

02234 5 TimeoutSet 10 EV_TIMEOUT_HANGUP

07312 5 tapie monitordigits 49 2

07312 5 LsPlayMsgFinished [1]

07312 5 TimeoutClear

07312 5 [fm Query] DB Query

07312 5 ODBC mode used

07328 5 About to execute Retrieve Operation [sELECT * FROM trial;]

27359 5 ERROR: OpenRecordset: Execution cancelled.

27359 5 TimeoutClear

27359 5 [Go Once More ?] Playing

27359 5 [Go Once More ?] Playing (C:\Documents and Settings\Administrator\Desktop\VOICE\PRESS 1.wav)

27421 5 PlaySoundStart ok [C:\Documents and Settings\Administrator\Desktop\VOICE\PRESS 1.wav]

27421 5 TimeoutClear

27421 5 RunModule PLAY end

27421 5 wa(3812,12737500)

27437 5 tapie callinfo MONITORMODES

27437 5 tapie callinfo MONITORMODES

32703 5 Play End line[5] (id=127375)

32703 5 LsPlayMsg EV_PLAY_FINISHED

32718 5 TimeoutSet 10 EV_TIMEOUT_HANGUP

32718 5 TimeoutSet 10 EV_TIMEOUT_HANGUP

43546 5 Timer fired EV_TIMEOUT_HANGUP

43546 5 LsPlayMsgFinished EV_TIMEOUT_HANGUP

43546 5 PlaySoundStop ok

43546 5 Hanging up call...

43546 5 TimeoutSet 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

43546 5 PlaySoundStop ok

43546 5 fnHangupCall end

43546 5 tapi Reply 66170 0

43546 5 tapie callstate IDLE 65982 0 0

43546 5 WorkingMode@Idle=

43562 5 TimeoutClear

43562 5 TimeoutSet 1 EV_TIMEOUT_TIMETOREINITLINE

44640 5 Timer fired EV_TIMEOUT_TIMETOREINITLINE

44640 5 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

44640 5 Initialise telephony (due to IDLE)

44640 5 tapic lineDeallocateCall(MainCall:65982) 0

44640 5 tapie linedevstate 2048 0 0

44765 5 Waiting for a call...

44765 5 hLine=66460

44781 5 TimeoutSet 5 EV_TIMOUT_ATERIDLE_ALLOWOUT

50250 5 Timer fired EV_TIMOUT_ATERIDLE_ALLOWOUT

Share this post


Link to post

Which version of VoiceGuide are you using?

 

Have you defined the Data Source using the "ODBC Data Source Administrator" ?

 

The name specified for the entry in the "ODBC Data Source Administrator" should then be specified in the VoiceGuide's "ODBC Data Source" text box.

 

A good test to see if the ODBC setup works is try to link to your ODBC Database using MS Access (using a 'Link Table') - if you have MS Access installed on this machine...

 

 

What is your 'ODBC Connect String' ?

 

 

Many people find that they have problems specifying the correct 'ODBC Connect String'... if this could be a problem for you I would try to test several possible variants of the 'ODBC Connect String' - most problems with ODBC connections are caused by this field not being specified as required by the DAO database drivers which VoiceGuide is using...

 

As a first thing I'd try doing is specifying the name of the ODBC driver in your connect string as well. This is what I found is necessary in some cases.

 

Below is a 'ODBC Connect String' for MS Access which shows how this driver name is specified:

 

ODBC;DRIVER={Microsoft Access Driver (*.mdb)}

Share this post


Link to post

Thanks for the quick response.

 

YES I have defined the DSN in ODBC administrator and have put the name in the databse name field in VG.

 

Here is the connect string, I am using currently, I have tried a few combinations and it doesn't seem to work.

Funny though, I tried an UPDATE and INSERT statement and they seem to work. Only SELECT seems to not work or its hanging up after trying for a while.

 

The same ODBC DSN works well when I connected the filemaker databse to other ODBC clients like ACCESS. There even the SELECT statement works fine.

 

Also if I use the an ACCESS linked table to Filemaker through ODBC and use that ACCESS table in VG it works but I really need to make it work directly with FILEMAKER nad since other SQL commands work fine, I believe SELECT statements should work as well.

 

Any help would be appreciated.

 

BTW: here is the current CONNECT STRING

 

ODBC;DSN=FM2;Driver={FileMaker Pro}

 

Thanks again for any help that you can provide.

 

AT

Share this post


Link to post

Have you tried any other SELECT statements?

How much data would "SELECT * FROM trial;" return?

 

Rather then selecting everything in the 'trial' table with "SELECT * FROM trial;" can you test with a SELECT statement which selects just certain columns from a single database entry/row?

Share this post


Link to post

YES HAVE TRIED A FEW SELECT NOTHING WORKS. ALSO THE TABLE ONLY HAS 7 ROWS.

 

HERE IS THE ERROR:

 

trial.`B`, trial.`C` FROM `trial` trial]

63578 5 ERROR: OpenRecordset: Execution cancelled.

 

THIS ERROR COMES AFTER A WHILE ( 3-4) MINUTES OF TRYING TO EXECUTE

43468 5 About to execute Retrieve Operation [sELECT trial.`A`, trial.`B`, trial.`C` FROM `trial` trial]

 

-THANKS

AT

Share this post


Link to post

A quick search on Google Groups using keywords "Filemaker ODBC" came back with a list of less then glowing comments about the Filemaker's ODBC driver...

 

We've managed to get VoiceGuide v4.8.45's ODBC interface going with a whole host of other databases' ODBC interfaces but maybe Filemaker needs something special that we don't know about...

 

Are you using the latest FM ODBC driver? (Apparently you can get updates from www.filemaker.com)

 

Maybe the problem with his ODBC driver occurs only when multiple rows get selected - have you tried using a WHERE clause in your select query which ensures that only one row gets selected?

Share this post


Link to post

YES, I AM USING LATEST DRIVER AND HAVE TRIED WITH WHERE CALUSE TO LIMIT ROW TO 1.

THE ODBC DRIVER WORKS VERY WELL WITH ALL OFFICE PRODUCTS (EXCEL, ACCESS) , ORACLE , SQL SERVER AND CRYSTAL REPORTS. I SEEM TO HAVE PROBLEMS ONLY WITH VG.

 

THANKS AGAIN FOR ANY HELP YOU CAN PROVIDE

AT

Share this post


Link to post

I'll see if we can modify VoiceGuide's call to the DAO's OpenRecordset() function (perhaps using different option flags etc) and have a new version forwarded to you for testing...

 

Possible workarounds that I can think of in the meantime would be:

 

A:

Use an ACCESS linked table to Filemaker through ODBC and use that ACCESS table in VG - as you have mentioned yourself.

 

B:

If you know VBScript you can write a short procedure which use ADO or DAO to perform the SELECT operation - this will allow you to experiment calling the OpenRecordset() function with various different paramaters and see which ones work in your case...

 

 

07328 5 About to execute Retrieve Operation [sELECT * FROM trial;]

27359 5 ERROR: OpenRecordset: Execution cancelled.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×