hi josh,

there isnt a way to specify a view in the SQL is there? therefore any time a query is referenced from a different query, it always uses the default view, right?

while it might be convenient here, isnt this behavior kinda of dangerous and potentially confusing? while it's not directly related to this situation, I had another example where the default view of a table had a filter applied. any lookups to that table were apparently using this filtered view as the lookup source, which meant some lookups appeared broken when they should not be. it just seems like the view is most appropriate as directing user-interaction, not necessary programmatic ones.