cjl

Steve, Fitch, Bcooney, thank you all for your replies. Steve - I've not had luck finding a good discussion of using find mode to improve layout switching. If you know of one, would you mind posting it? I had been looking to generate an empty set before creating a record in the hope that will reduce data transferred from the server. (i.e. no, not searching for a particular record) Thank you for the link. I am comfortable making TO independent field references, however the duplicated line is a 'Perform find' script step. I didn't know of any way to generate an empty set without tailoring this to a specific TO. However reading Fitch's reply, it sounds as though a blank layout rather than a null find is the sensible approach. Fitch - thanks for the video. It's good to get confirmation that an empty field means no server - client data transfer. Yes, I do use 'new window using layout' rather than 'go to layout' script steps. Apologies for not making that clear. If moving to a blank layout, is there any additional benefit in doing so in find mode? I'd only been doing so to avoid loading any data from the destination table. If a blank layout solves that same problem, perhaps switching in and out of find mode is unhelpful? Bcooney - thank you. Until recently I'd have used a similar (though less elegant) technique for almost all record creation. A TO and a relationship wherever I create records has left me with relationship graphs that are rather busy. Layout-hopping creation scripts for less frequently used processes seemed to me to be one way to simplify the relationship graph. But at heart, I just don't know the impact that a great many (say approx. 100) single-use TOs and relationships have on performance where there's high server latency. Do you have any insight into this?

Hello all! I'm working on a very high latency solution. A server in Germany, clients in East Africa. I've a number of scripts that involve a (scripted) move to a different layout, record creation and a return to the original layout. In an effort to speed things up, I've been trying to reduce the data requested from the server by entering find mode before switching layouts, getting an empty found set (say by searching for an empty key field) and then creating any records. If there's anyone who uses this (or a similar) technique and has some feedback regarding performance, I'd be very interested to hear about your experiences. And regarding this particular method, does anyone know of a table occurrence-independent way to obtain an empty found set? At present I'm tailoring each find request to a specific TO which results in some duplicate code.