I've been posting questions and thoughts regarding scheduling problems
lately and get heaps of good answers. Thanks! I thought I'd post a tip
about how to approach solving problems. A lot of people do the same
thing I do and I've posted regarding this before, but here goes.
When I've got a new problem to solve, I _very_ often launch 4D and
create a brand new database. Why?
* I feel totally free to experiment and make mistakes. Who cares? I'm
throwing this database away soon enough.
* I can cut corners and save time. If I need a form, I don't need to
make it pretty. That's harder to resist in a real database.
* I don't get caught up on weird interactions between the existing
code in the main database and my test code. I've been burned on that
one way too often.
* I remain focused on the problem at hand.
* I don't have to make the code exactly how it will be - just good
enough to figure out how things will work.
Once I've learned enough, I can copy over any useful bits and pieces
easily enough.
Anyone that hasn't done this - or has forgotten to do it - think about
it next time you've got a fresh problem. It's kind of fun! This
particular style also lends itself well to building components in V11.
As far as I can tell, components are the best thing to happen to 4D in
a long time so people should really try and make some time to get
comfortable building them.
**********************************************************************
Get up to $600 to spend on Amazon.com
this holiday season -
http://www.4d.com/serverpromo.html
4D Internet Users Group (4D iNUG)
FAQ:
http://lists.4d.com/faqnug.htmlArchive:
http://lists.4D.com/archives.htmlOptions:
https://lists.4d.com/mailman/options/4d_techUnsub: mailto:
4D_Tech-Unsubscribe@...
**********************************************************************
