[AccessD] Why use UDF function as listbox RowSourceType??

This is sitting untouched on another list. Any takers here?

> I have been following the documentation here and here
>
>
>
> http://msdn.microsoft.com/en-us/library/office/ff821440(v=office.15).aspx
>
> http://msdn.microsoft.com/en-us/library/office/ff845731(v=office.15).aspx
>
>
>
> and trying to understand why someone would want to do this, rather than
creating a temp table with the results of whatever is used to get the
values.
>
>
>
> What I do not like about the method – aside from it being inordinately
complex and to me, non-intuitive (though I eventually got it) – is that it
is called again and again while the user scrolls the listbox, which slows
down the application.
>
>
>
> Why do great programmers use this technique?
>
> (I have seen code for example by Wayne Phillips at EverythingAccess.com
>
>
>
>
http://www.everythingaccess.com/tutorials.asp?ID=Accessing-detailed-file-information-provided-by-the-Operating-System
>
>
>
> where he uses classes to wrap the functions to grab file properties from
windows explorer, and when he lists the results he uses a callback udf
structure similar to that shown in the above links).
>
>
>
> Is there some compelling reason to do it this way, rather than a temp
table?
>
>
>
>
>
>