Connecting to SQL in Runtime Environment (MS Ver 10)

[PhotoHogs]

Hey everyone, thanks in advance for your help.

I have a Access Ver 2010 database that is currently deployed on an internal network. We have the typical Front End / Back End with our back end sitting on a network drive that we all connect to (6-8 users). In order to allow our field staff to read data we have moved a few tables from the back end to a SQL server, but not all tables. These tables are then connected back to the front end using an ODBC connection. I have been testing this over the past few weeks and finally got everything set up and am ready to deploy the new front end to the rest of the office.

My issue is that I use the full version of Access, the rest of the staff here uses a runtime version so as soon as I tried testing we got a runtime error. GRRRRR. The front end allows us to sign on to the back end but then when it asks for the credentials for the SQL Server, that's when it crashes on runtime. On full version it runs fine.

I have defined a machine data source on the computer using runtime and tested the connection, it works.

What am I missing here? Any help would be appreciated. I really don't want to upgrade the rest of the users to a full version if I don't have to.

Thanks

[ranman256]

Do the users having runtime have their ODBC connections set to ALWAYS REMEMBER PASSWORD to the SQL svr?

Also, there are a few commands that Full access allows, but will snag on Runtime (I found that out) If you can trap WHERE its hitting the error. Maybe a (msgbox err.description,,err) in the trap.

[PhotoHogs]

FIXED.

the OBDC was not set up properly. My mistake.