I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
Solved
SQLFETCH not bringing back data
Best answer by Jonathan Smith
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
The SQL server DOES NOT have to reside on the same server as UniData, Can you point me to where in the documentation where it states that as it is incorrect. The early references in the EDA manual are below, and they DO NOT state they have to be on the same machine.
Page 15 States "The external database server can be on the same machine as the U2 server or on a different machine. However, the external database client must be on the same machine where the U2 server is installed."
Page 16 States "The U2 server can reside on UNIX, Linux, or Windows. After the SQL server, Oracle, or DB2 database server is installed, the appropriate ODBC driver must be installed on the U2 server machine"
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
My tears have dried. Going forward _ everything now is JSON, REST, GraphQL, etc.
- Rocketeer
- 356 replies
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
I just checked and we do have EDA, I’ve just never used it before. Can you point me in the right direction for which UniData manual will cover EDA for beginners? An EDA for Dummies? LOL
- Rocketeer
- 356 replies
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
I have attached it to this message for you, but thought I'd give you the reference in case you wanted updated manuals for other subjects as well.
In terms of giving a bit more assistance on getting up to speed with it then if you happen to know who your Rocket Account Manager is I can drop them a note and see what we can get arranged for you.
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
- Rocketeer
- 356 replies
- Answer
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
The SQL server DOES NOT have to reside on the same server as UniData, Can you point me to where in the documentation where it states that as it is incorrect. The early references in the EDA manual are below, and they DO NOT state they have to be on the same machine.
Page 15 States "The external database server can be on the same machine as the U2 server or on a different machine. However, the external database client must be on the same machine where the U2 server is installed."
Page 16 States "The U2 server can reside on UNIX, Linux, or Windows. After the SQL server, Oracle, or DB2 database server is installed, the appropriate ODBC driver must be installed on the U2 server machine"
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
I'm working with UniData 8.2. I've written a utility that lets me view and treat an SQL table like it was a local UniData file with UniQuery type commands.
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
It's been working fine. But I am having an issue with one ODBC connection that sends back the rows but not the data for the columns.
Has anyone seen this before? Could it be some type of privilege setting? I can get data back using an SQL manager tool using the same logon credentials.
SQLFetch doesn't bring back any error messages, just no data.
I am going from one domain to another, all within our intranet.
Thoughts?
Are you using BCI to connect to SQL Server on Windows UniData 8.2 server? You might test the SQL statement outside UniData Server first. Please create a System DSN to connect to SQL Server first. You can use the UniData CONNECT command to test the SQL statement against SQL Server.
Paul
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
