hi, just checking whether this is expected weirdness:
I am running a union query involving a table designed with lookups*. Two looked-up fields in that table are requested in the query and when I run either branch of the union individually, the looked up info in both fields is returned.
However, when I run the unionised query, one of those fields comes back with lookup data and the other comes back with the ID data, and for the life of me I can't work out why.
The other tables that are joined in each branch of the query don't have lookups, and in the table that does, both the lookup combo boxes use simple Id-Name matching queries
Been trying to work this out all morning and I'm stuck. Hopefully those that know access can tell me whether this is behaviour i should investigate further or whether I ignore it as a 'quirk' of the system.
tia
mcalex
*yes, I know, but I inherited it, and can't change things just yet
I am running a union query involving a table designed with lookups*. Two looked-up fields in that table are requested in the query and when I run either branch of the union individually, the looked up info in both fields is returned.
However, when I run the unionised query, one of those fields comes back with lookup data and the other comes back with the ID data, and for the life of me I can't work out why.
The other tables that are joined in each branch of the query don't have lookups, and in the table that does, both the lookup combo boxes use simple Id-Name matching queries
Been trying to work this out all morning and I'm stuck. Hopefully those that know access can tell me whether this is behaviour i should investigate further or whether I ignore it as a 'quirk' of the system.
tia
mcalex
*yes, I know, but I inherited it, and can't change things just yet
