Hmm, a SETALL for BINDEVENTS Has some possibilities.

Actually, where I have used that other technique that I suggested was exactly for just such a tool as you're describing. We stored the "translations" and other specified properties that needed changing and loaded them all in the baseclass form init from a table. Happens so fast, it added only negligible overhead to the form start up time. All the translations were done in VFP, with all VFP code, and was a tool that was part of the application. All under user control. It essentially was a simulated Form Designer in the application itself.


>What we need is a SETALL equivalent for BINDEVENTS. <g> Anyway, this is only needed during development so objects can be repositioned on the running form where captions are changed. Currently, this is done with code in the RightClick of every object in my baseclass library --
>
>if version(2) = 2
> do form Translate
>endif
>
>The first form has to be running so my language translation code is fired and has translated all the English strings to Spanish or whatever other language. RightClicking on any object brings up a builder form where I can dynamically change the Top, Left, Width, etc. properties of the object that I just clicked. This way I now have a form whose objects are positioned correctly with respect to the language being used. Once all the different language properties are recorded, I no longer need the RightClick method in every object.
>
>>I've always dealt with something that has to have control over everything like that by putting a transparent shape object over top of everything and passing and clicks, etc., to the control under the shape as needed. I don't have access to any example code for that at the moment, but that's probably a lot easier than trying to bind to everything at runtime.