# ODBC communication with Community version of Natural

**URL:** <https://techcommunity.softwareag.com/t/odbc-communication-with-community-version-of-natural/75505>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-on-Linux, Natural-on-Windows-Unix\
**Created:** [October 16, 2007, 1:18pm UTC](https://techcommunity.softwareag.com/t/odbc-communication-with-community-version-of-natural/75505 "2007-10-16T13:18:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tony5](https://avatars.discourse-cdn.com/v4/letter/t/e68b1a/32.png) [@tony5](https://techcommunity.softwareag.com/u/tony5)\
**Post date:** [October 16, 2007, 1:18pm UTC](https://techcommunity.softwareag.com/t/odbc-communication-with-community-version-of-natural/75505/1 "2007-10-16T13:18:33Z")

</div>

Hi, I recently downloaded the Community Edition of Natural from the SAG web site. The installation went well and seems to be working fine with the equivalent version of Adabas. I then discovered in the manual that it would be possible to access databases, eg. Oracle, via ODBC. At first I thought I had to install Entire Access but, and maybe this was a misunderstanding of the documentation by me, it looked like it was possible. I defined the database to ODBC and performed a test connection and that went well. I then updated the “Natural Configuration Utility” with an entry in the DBMS assignments that looked like the following:

DBID=20, Type=SQL, Parameter=ODBC:name (name being the name I had entered in the ODBC defn. above).

I then restarted Natural. When attempting to create a DDM pointing at this database I was prompted for the Owner and Table names which I entered \* into both. When I selected OK, I received a NAT6386 error “Logon to SQL database failed”.

The Oracle database is a remote database, which is why I initally expected to have to install Entire Access but the documentation seemed to imply that ODBC connectivity was acceptable without Access. I ran an ODBC trace and discovered that Natural had not communicated with the ODBC driver at all.

Has anyone tried this before? Is this a misinterpretation of the manual on my part? Do I have to install Entire Access?

TIA,

Tony.

---

<div class="post-metadata">

**Author:** ![anon29934956](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@anon29934956](https://techcommunity.softwareag.com/u/anon29934956)\
**Post date:** [October 22, 2007, 2:12pm UTC](https://techcommunity.softwareag.com/t/odbc-communication-with-community-version-of-natural/75505/2 "2007-10-22T14:12:48Z")

</div>

Hi,  
Natural Windows always require Entire Access to access SQL DBMS.  
Regards,  
Michael

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:48pm UTC](https://techcommunity.softwareag.com/t/odbc-communication-with-community-version-of-natural/75505/3 "2021-04-02T14:48:49Z")

</div>