Thank you for your response. I was wondering if I was going to get one. There were a bunch of views but yours is the first response.
A little more background and some questions;
By "...use ODBC..." you mean set up an ODBC datasource using the Windows ODBC Data Source Administrator utility and then using that in my .accdb file to connect to my database. Is that correct? If so, that's good - that's what I've done. To be clear. That's what I've done for the DB that I'm building the App for. The data for the look-up is actually coming from another database on another server which is linked to my DB through linked servers.
As I mentioned, I had tried creating a view on the server but still received a message indicating that it didn't like the FROM statement.
I didn't think of creating a link to the view in the .accdb file, rather, I was just calling the view directly. I will try that and report back.
With respect to using an .adp Vs. a .accdb I am aware that MS is dropping support for the .adp - which in my view, is regrettable. They're just so easy to use, and light weight - one database engine slowing things down rather than two etc....
The whole reason for the post was that, in consideration of the inevitable demise of the .adp I am trying to use a .accdb and ran into this roadblock.
Since the data that I'm using to populate my combo-box lookup comes from a different database than my app do I need to create a second ODBC datasource and use that or can I use the view (via a linked table in the .accdb)?