datAdrenaline
AWF VIP
- Local time
- Today, 08:57
- Joined
- Jun 23, 2008
- Messages
- 697
Hello Chris
Thanks for the clarification ... eitherway, with the hidden reference, it is completely possible to code in such a way to NOT require an explicit reference to DAO, as you pointed out earlier in the thread. I just used variables declared as objects, where as you did not to use variables at all ... a very clean technique indeed, and one that I use often. And to give credit where credit is due, I beleive your conversations on the 'With CurrentDb ... End With' construct, are what increased my used of such a technique as I found it to be an effective way to code.
Whenever I have removed the explicit reference (albeit rarely have I HAD to do so ...) I like to put in comments what each object variable will become or what each constant represents, thus my example.
But ... in 98.99% of the apps I create, I have both ADO and DAO explicitly referenced
... but the situation posed by the OP seems to definately call for a dropping of the explicit DAO reference.
Thanks for the clarification ... eitherway, with the hidden reference, it is completely possible to code in such a way to NOT require an explicit reference to DAO, as you pointed out earlier in the thread. I just used variables declared as objects, where as you did not to use variables at all ... a very clean technique indeed, and one that I use often. And to give credit where credit is due, I beleive your conversations on the 'With CurrentDb ... End With' construct, are what increased my used of such a technique as I found it to be an effective way to code.
Whenever I have removed the explicit reference (albeit rarely have I HAD to do so ...) I like to put in comments what each object variable will become or what each constant represents, thus my example.
But ... in 98.99% of the apps I create, I have both ADO and DAO explicitly referenced

Last edited: