@Poweruser
First let's look at the term QueryDef. Since you need to Google it, it must not be as obvious as I'd expected. QueryDef is simply the correct term for the queries that are saved in an Access database. Every saved query is a QueryDef. A Query is a looser term which covers QueryDefs, but also SQL strings called from within code in Recordsets etc.
@Poweruser
The bump is probably not too early, but as I haven't yet had a chance to look at your previous post, was probably unnecessary. Certainly not a problem. For your peace of mind though, remember that forum based web posts are picked up as and when by various different members. For instance, I may well take a few days off sometimes if I go away from home for any reason. A lack of response for many hours, or even a day or two, doesn't necessarily mean a lack of interest or intention, just that this has to fit in with other things.
@Poweruser
One thing to bear in mind, is that the fact that this is managed by a back-end server means that any permissioning done there will effect such queries. One user may have different rights from another, so it may work correctly for one but not the other. If you're using linked tables though (where the linking is managed outside of the QueryDef object), it should all work pretty smoothly.
@Poweruser
Very kind of you to say so, but from what I see of the Access MVPs, they contribute more than I do at a professional level. This is just a hobby for me. I enjoy it of course, but cannot devote enough time to it even to be considered for that.
On the thanking side, a little note of thanks, as you've done, is always well appreciated :) Aside from that, if you feel an answer (post) particularly hits the spot then you can select it as the best answer. It's always nice to see one of your posts has merited that.
12
