Hi George,

>These are very much in-line with my thoughts. The problem I find with workarounds is that sometimes, after a version change, they become "don't work" arounds. :-)

I 100% agree with you.

>I think it simply reinforces what I've been saying in this thread. If we could assign the DE at runtime, then some of these problems would disappear. Tie it to being able to visual design it during development, I think would be a big plus.

Lets wait till VFP7. This could be asked for and is a very valuable functionality for any developers.

>This following part isn't directly in response to your post (just kinda me gripping). I find it very strange that the DE isn't documented better. If you pull it up in the help file, no methods are listed. True, they're in the help file on their own, and related back to the DE, but the only way to get a list of them is via AMEMBERS().

Infact it is very difficult for beginners to get the concept of the DE being as a class in itself. It is true that the DE is not documented well. The help just displays the Events and Properties and they have not changed the help in VFP6 either. Not that we would expect them <g> but a white paper on it would be very helpful to developers.