I really want to place a bunch of our code / forms into a component. It will make it much easier to install into other systems, and to update that code / forms as into older designed system that use an older version of the component. Of course it also protects what could otherwise be unprotected code.
What sources of good information are there other than 4D’s Component documentation in the manuals? I expect I will comb through the inug and Knowledge base when I run into problems. From the number of questions I see here, it looks like the component pitfalls are not documented well. I know as I started to read the documentation - within the first page they introduced a term ‘matrix databases’ that was not defined as to how they are using it. The sentence then became meaningless - hate writing like that. It is a great concept, and has matured over the years, and many are using it successfully. It is past due for me to jump into that pool too. Thanks Jody ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
