I agree it could be handy to allow end users to change the translations. I've
extended this solution for another customer who required the option to add new
languages to their (intranet/internet) site without designer interference.
Besides the drawbacks mentioned (you could force the user to enter the correct
translations and/or do a conversion when implementing new versions), there's of
course the 64k limit. The method described was developed for a large
application with lots of translations. If we wanted to use lookups, we'd have
to split them, which would make this method much more complicated to implement.
I agree it could be handy to allow end users to change the translations. I've extended this solution for another customer who required the option to add new languages to their (intranet/internet) site without designer interference.
Besides the drawbacks mentioned (you could force the user to enter the correct translations and/or do a conversion when implementing new versions), there's of course the 64k limit. The method described was developed for a large application with lots of translations. If we wanted to use lookups, we'd have to split them, which would make this method much more complicated to implement.