ODBC and Access 2010 Runtime (1 Viewer)

I am using the Access 2010 runtime module but I have bumped into an issue.

Here is my problem, I have a few dozen external SQL tables on our minicomputer I am linked to with the ODBC link in Access 2010. It seems in 2010 Access makes some new types of ergistry entries or something. Enough to say that to establish the links on a clients computer I have to install the full version of access create the links and then run the access code. This sort of defeats the purpose of the access runtime in the first place.

Question is how do I set up the ODBC for access 2010 runtime?:banghead:

I'm assuming that the runtime version is linking to a different source than the development version. Runtime only allows you to run access, not use any of it's facilities such as linked table manager.

To get round this you need to build the equivalent within the runtime version. How you do this depends on the requirements. Two solutions spring to mind.

1. use VBA to either create a tabledef linking to the ODBC files or to modify an existing tabledef - this should point you in the right direction

http://msdn.microsoft.com/en-us/library/bb220949(v=office.12).aspx

2. use sql to create a dsnless connection in your queries - here is a link to where you can define these

http://www.connectionstrings.com/

You have failed to present the actual specific symptoms causing whatever it is they cause, so it is not easy to help. Do not interpret but be specific - what do you do and what does the system do.

If I was playing Jepordy, I would have rang-in last! The above two beat me to a response! LOL

Search the forum on DSN-Less
I think there was a question about last month.

Basically, use code to create a Linked Table in the Access objects rather than the ODBC Connection for the workstation.
Here is a recent post with various code examples to get you started:
http://www.access-programmers.co.uk/forums/showthread.php?t=270468