Sorry, no I mean that I'm prompting from the 3rd party client. (i.e. in MSAccess, the selection criteria is [Please enter the fiscal year] ...or something to that effect... which would bring up the dialog box for the person running the query.
In that example, if I enter 2004 in the dialog box, I get the error. If I enter 2004 into the selection criteria itself, the query works. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alfke, Colin Sent: Tuesday, January 18, 2005 9:54 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UniData ODBC / Prompt for selection criteria Do you mean you're trying to do an <<inline>> prompt through an ODBC connection? You're a brave soul. I would prompt for imput in the 3rd party client and pass the full string through... hth Colin Alfke -----Original Message----- From: Amy Cook I know this issue has been reported to IBM (don't know what IBM calls it, but the 'bug' # is 144655). I'm trying to figure out if anyone has a workaround (or if this has been fixed at a later version). When I prompt for selection criteria from a 3rd party client (i.e. Access), the unidata odbc driver returns an error message - ODBC - Call Failed. If I hard code the answer to the selection criteria, instead of prompting for it, the query runs correctly. We're on version 5.2.8. Suggestions? [demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
