Attempt to query linked tables failing

[gnrmjd]

Ahh interesting. Ok. That sounds good. Thanks for all the help, I'm going to look into doing it that way, like you said. I'm a little worried because the application that I'm replacing with Outlook that my company had already, was doing a similar thing - making queries dynamically based on user input, and it was very slow.

But we were thinking of making some views and things to help with the speed since the tables are so large and not all information is necessary. I'm just worried that if I do queries without any thinking about how to optimize them it could be still just as slow, but I think it's still worth it to move to outlook because of the customizable user interface.

[JoeM]

One last thing, just to clarify, when I talk about building the queries dynamically using VBA via Form selections. Typically, what I do is use the Form selections to build the SQL code that I need (using VBA), and then I assign that SQL code to a pre-existing query name (that I just keep overwriting every time). So the resulting query itself is "self-contained", in that it doesn't include any references to any Forms or anything like that. And I can easily return the results quickly by opening the query in my last step.

As far writing Access query code via VBA (if you go that route instead of using a pass-through query), to get the Access query syntax, I find it very helpful to build a "sample" query that does what I need to do, then switch it to SQL View, and use that code as my guide for building the code in VBA.

Best of luck, and remember, you can always post back to this forum if new questions arise.