>If they did care, some of these things could have been added instead of >querying on object fields that most people will eventually wish they didn’t >use in the first place.
This made me smile a lot. I had exactly the same thought. It brings back memories of subtables which I'm sure every 4D old-timer regrets ever using, if they ever did. Someone could compile a list of 4D features with a recommended "steer clear of this to avoid regret later" ;-) To add my 0.02p on components:- No. Don't like them. Don't use them in our coding. I'd only ever use them for an essential 3rd Party "drop-in" black-box component that I have no intention of amending the source code for, so much akin to plug-ins. Other than that, I can only echo what others have said about wanting the 4D language moved forward a bit. I do recall that 4D did say at a Paris Summit that they had decided to re-commit to the 4D language. Adding multi-threading support is possibly a sign of that decision, even though I really dislike their implementation of it. Best regards Keith White Synergist Express Ltd, UK. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
