ODBC Configuration Settings for SQL 11 Anywhere (Windows 7 32 bit)

[Former Member]

I have setup an ODBC entry for SQL 11 Anywhere, I select integrated log in as I dont want users knowing what the password is. I try run my app which first connects to DB to process...connect failed. Go back into ODBC setting, it has entered in the default dba, sql username and pwd and although I have changed, saved, rebooted, deleted added again ...NADA. I tried editing in registry ...and it still changes the settings in Windows 7....this is SO annoying. Short from changing my application to connect without using a DSN...can anyone tell me if I am doing something wrong. I have registered the dbodbc11.dll already with regsvr32.exe. Any ideas?

[MCMartin]

I am using Windows 7 64 bit without the described behavior (32 and 64bit ODBC)

[MCMartin]

Are you sure, that your Win 7 is 32 bit: your observation 2. is usually a hint, that under win 7 64 Bit you are using the wrong odbccad tool to view the odbc settings.

[Former Member]

It's definitely 32 bit.

[jeff_albion]

"Integrated Login" means that you're trying to use the Windows user login information to log in to the database. The database must be explicitly set up to use this information (by setting the appropriate database options) - are you really trying to do this? Or is your database really set up to use the 'Standard' log in feature?

---

[Former Member]

It worked fine on Win XP...it's JUST windows 7 that doesn't work..

[VolkerBarth]

As you say you can connect via DBISQL - do the database engine and the client/DBISQL run on the same Win7 box?

And what does the following query return?

select * from sysoption where "option" = 'login_mode';

As DBISQL works, does dbisqlc work with this DSN, too?

(Note: FAIK, DBISQL uses JDBC and dbisqlc uses ESQL, so both do not really use ODBC but can use the ODBC DSN to build a connection string - so their successful connection is not a full hint. Nevertheless, they should treat a DSN just as your app should do.)

[Former Member]

Ran it now...shows 3 columns

1st - user_id = 2 2nd - option = login_mode 3rd - setting = standard

Yes they run on the same Win 7 machine

[VolkerBarth]

Well, then obviously you do not have integrated logins enabled, as that should contain 'Integrated' in the setting column. So, how do you connect via DBISQL?

See Jeff's comment above how to enable integrated logins.

BTW: To respond to a comment (instead to the whole question/answer), you can use the "Reply" button right below each comment. That makes it easier to follow nested discussions...

[Former Member]

to get into DBISQLC, I type in the UN and PWD, then choose the DSN name from the drop down list. The App however doesnt require a UN and PWD.

[VolkerBarth]

So obviously you use a standard login (with UID and PWD) to connect from dbisqlc.

I still suspect that the database is not configured to allow integrated logins. Have you tried to follow Jeff's suggestion?

[VolkerBarth]

Just a few hints:

1. What error (SQLCODE) is returned by the application that fails to connect?
2. If you check the DSN in the registry, can you assure that there's the "Integrated=YES" setting?
3. And do you use an user or a system DSN?
4. Or is there a SQLCONNECT environment variable set (check with SET in a cmd shell) that might add a default UID and PWD?

[Former Member]

1. Failed to connect to database
2. Yes Registry is right, but in Windows it's wrong.
3. System DSN
4. Checked and no, no variable SQLCONNECT even listed.

[VolkerBarth]

What happens when you use DBISQL with the same DSN to connect?

[Former Member]

Connects fine