>>Personally I think that's a bug in Visual FoxPro.
>Rick,
>I believe with this opinion you are standalone shouting.
>Regards,
>Koen


Okay.

Well, I'm not sure why you posted this, Koen.
Or what "standalone shouting" is. I was done
with my responses on this issue.

I will now add:
Visual FoxPro is/was amazing. But Microsoft
did get several things wrong with it. I will
try very hard to correct those issues in Visual
FreePro, and foster the ability for others to
step up and guide the project by making all
source code available.

Examples:
mDot (as implemented).
Containers (as implemented).
Timers (as implemented).
READ EVENTS.
Commands like PUBLIC and Axxx() not overriding the destination variable type.
Ghost objects lingering around after deletion if they were declared at design time.
Requiring classes for GUI refactoring.
Requiring explicit conversion on variable types.
No built-in remote table facilities apart from LAN-based shared access and SQL pass through.
Almost no graphics support.
No animation.
Almost no sound support.
No easy multi-threading.
A limited grid.
Limited base classes.
No easy override for custom drawing base classes.
See more here: http://www.visual-freepro.org/wiki and look for changes and VXB++ near bottom of main page.