Noah: Can I make a suggestion for you that I and many others here do in their code:
1. Have very defined naming convention of your variables in code. 2. The naming convention must clearly show the type of variable. 3. Every method must declare its local variables. 4. Every process variable must be declared int the Compiler_ProcVar method 5. Every Interprocess variable must be declared in the Compiler_IP_Var method 6. Anytime you start a new process ensure that you call the Compiler_ProcVar method. 7. When you start the application call the Compiler_IP_Var method. 8. For every method ensure to add an appropriate entry in the Compiler_Methods. Certainly this is daunting if you have not done it before and you have a lot of code. Once you get it done though it makes things work for you so much better. Your code will work more consistently. An added advantage is that you can write a method that you can run each time to modify a method (in the sense of adding or modifying) a variable. This method will go through through your code, delete all the variable declarations, and then recreate them as appropriate and place them in a preferred order. This makes coding so much simpler. I now do not have to spend the time writing out the compiler declarations, or managing the modification or deletion of them. The method does it all. I know this does not get you through what you need right now, but it is likely what you need to get done ASAP. Sincerely Jody Bevan Argus Production Inc. > On Jul 31, 2018, at 3:46 PM, Noah via 4D_Tech <[email protected]> wrote: > > Good afternoon, > We are in the process of converting an application from 15 to 16 and one of > the first errors that we have encountered came from a line that was setting > the query destination into a variable. > > The variable was declared in the on Load form event, and this code has > worked without a problem for many versions back. > > I was able to quickly bypass the runtime error by moving the variable > declaration out of the conditional block which only ran once (when the form > loaded) into the form method itself (not wrapped in a conditional). Rather > than blindly make a change, we would like to have a solid understanding of > what changed from 15 to 16. > > I have combed over the changes listed here: > http://doc.4d.com/4Dv16/4D/16.3/Conversion-to-4D-v16.100-3673248.en.html > specifically: > http://doc.4d.com/4Dv16/4D/16.3/Changes-in-behavior.200-3673250.en.html > > ********************************************************************** 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] **********************************************************************
