> This sort of goes to the heart of what I'm wondering about - if the table > names have any hard relationship with the structure? I'm assuming they > don't, that they are like the method names and 4D tokenizes them internally > and puts on a friendly name when humans are involved.
There are other people that can say more about the internals, but I can say what I see as a 4D coder: * Create two methods with the same code. Something that uses a field like: [Species]ID:=5 * Now close one method and leave the other open. * Go to the structure editor and rename the field something else - say IDX. * Now look at the code in both methods. The one that was closed has the new field name, the one that was open does not. 4D presumably parses the method when you close it, finds the right [Table]Field name and stores table and field number. When the method is opened and translated for display, the current name is expanded. It's been this way since forever. Embedded SQL and any sort of text-based/external code don't have a way of taking advantage of this feature. (Although for the embedded SQL, it could be added.) ********************************************************************** 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:[email protected] **********************************************************************
