Hi all -- I'm trying to resolve a limitation in Access regarding how it handles programmatic select queries -- e.g., where the select query and related code to pull it are embedded in a procedure. My question is specific to how the select query pulls information from lookup tables in this context -- in the attached example, I have a Table1 and Table2. Table2 provides a lookup value to the records in Table1 (in this example, astrological signs). In a normal (e.g., non-programmatic) select query, the results would display as text (Pisces, Taurus, and so forth). However, when executed programmatically, the index values themselves display (1,2, 3). My workaround for this is to create a second query which uses the results of the first to grab the associated text value from the supplied index value after the first query returns results. Clumsy, but it works. However, I'd like to know if anyone has a more elegant way to restate the original select query to just pull the text value out without having to resort to a second pass. Access doesn't accept the usual trick of using syntax like Column(2) that can be used with combo boxes.
For the record, I'm not interested in discussing why I want to do this, just suffice it to say that I do and therefore, I'd like to explore resolving my question. Thanks in advance for your help.....!