>>For example, rather than defining UDF's as some external module outside of
>>the database. How about storing the module in the database and then the
>>database will, according to each platform's dictates, give the module disk
>>presense as required and load and make use of it dynamically.
>>
>
>This is the way it has always worked.

I'm confused then... Why do I have to make sure there are DLL files in just
the right spot or InterBase barfs when I access a UDF? Why isn't there some
way that InterBase seems to actually stored the contents of the UDF rather
than just a reference to it externally?

I generally avoid using UDF's and such so I am no authority on the subject.
I could be totally off here.

Thanks,
Jason Wharton
InterBase Developer Initiative
jwharton@...

InterBase will be the database of the new millennium.