First to Stefan: Thanks for taking on the task as Leader of the UDT project team, and to Leupold: Thanks for your yearlong effort!!

I would use this opportunity of team leadership change to propose two improvements:

1) Transfer the whole UDT solution over to SQL on a permanent basis. This has been proposed by many others before, without any help. The major argument for basing UDT on SQL is that SQL after all is the standard databse of DNN as a whole. Also it would do it much easier to integrate UDT with other modules like report etc, AND make the data much easier accessible. Also, the free SQL UDT module that earlier has been developed as an independent offspring, has seemingly proven that the transfer would be fairly easy. To get UDT over to SQL is in any respect simply pure logic.

2) Follow DNN standards for user role defined field settings, so that one for example can create fields that are completely hidden from certain user groups, but edible or readable for others, based on admin settings. Today's open indescreet solutions is sorry to say unprofessional - and I can't see that they meet normal DNN security standards.

As of today, I'm stuck with the older 3rd party and only semi-working SQL-version of UDT, and would jump of joy if these changes were made to the official UDT-module, but maybe I'm asking too much of a a free module in an open source system?

Humbly yours, OJ, Stavanger, Norway