If the expected result set is in the range of "[Array:553x36]" I would
suspect characters that the ODBC/JDBC connector can't pass or parse.
Is it reasonable to refill the database with values not containing
special, symbol, or punctuation characters to diagnose?
Had a similar issue with a FM
Wayne,
First do a simple query like "SELECT 1" just to double check the DBMS.
Then try grabbing just one row "SELECT packagename FROM Packages WHERE
packagename = '{known name}'"
If that works, then we may be looking for a bug dealing with non-value. Try
"SELECT packagename FROM Packages
Wayne,
I recall needing to adjust datatype(s) in FM databases to work correctly
with Wtango and JDBC/ODBC.
Perhaps a test FM db with only integer columns.
- Steve K
On 7/10/19 7:06 PM, ubslab wrote:
> Wayne,
>
> Are you able to connect to FM table.columns in the Terascribe editor
> JDBC/ODBC
I hadn’t noticed the user vars previously. They are left over from previous
searches with the Search action. I added a Purge as the first action and they
no longer appear.
I also changed the Select to retrieve a field that is not user generated, so
more predictable and alphanumeric.
Still
> On 11 Jul 2019, at 12:38 am, Robert Shubert wrote:
>
> Wayne,
>
> First do a simple query like "SELECT 1" just to double check the DBMS.
I tried:
SELECT 1
SELECT 1 FROM Packages
both gave an error.
>
> Then try grabbing just one row "SELECT packagename FROM Packages WHERE
> packagename =
> On 10 Jul 2019, at 4:26 pm, ubslab wrote:
>
> Wayne,
> So none the following forms will work in the action?
>
> SELECT packagename FROM Packages
>
Error
An error occurred while processing your request:
File: SQLfindpkgs.taf
Position: Direct_DBMS
Class: Internal
Main Error Number: -101
