and... can I fix the typo in the post heading!!  LOL

If not enabled, the ODBC security settings should not be required.  Sometimes there is phantom data, if the option was enabled in the past, but that is rare.

Permissions to create a DSN are up to Windows / domain settings, not Sage.

If using Advanced / Standard, use SOTAMAS90 (32-bit DSN which is auto-created by the workstation install). You can install the 64-bit ODBC driver too.  Adding new DSN's (with SOTAMAS90 as a template) are done easily, if you want to create Silent DSN's.

If using Premium, all ODBC connections are through SQL (assigned database permissions in SQL are separately managed from Sage logins).  Use Google if you need help with SQL ODBC.

Thanks.  I'm having problems getting any of my "regular" user id's to work.  My consultant setup a dsn on my desktop using the smg login, and it's working great.  I just can't get other users setup...  not even my user ID.  In DSN setup, I presume the user id is the 3-digit user CODE?  or is it the user logon name.

It's the login name.  If you use integrated authentication it is your Windows login (and the password is likely blank).

ok.  I have no idea why it's not working.  when I do the "Test Connection", it then asks me to login, so I'm presuming something is wrong with the login authentication (not using integrated authentication).  I've tried both the login name and the code, and neither work.... I can't understand what else may be preventing this from working.

And the connection succeeds when I enter the company, user id, pw in when prompted in the "Sage 100 Database Signon" window that appears when I try to "Test Connection" (which shouldn't appear if the username/pw in the dsn is setup properly.

Problem resolved.  Both of the users I was testing had semi-colons in their passwords.  When I tried to authenticate with a different username/pw that didn't use semi-colons in their password it worked...  Go figure....