Hello All, Overall, this seems to be the biggest bug-a-boo (so far) as I try to migrate a pretty elaborate application.
I've been reading feverishly -- white papers, manuals, books -- and I haven't read the "perfect explanation" of this new paradigm. I tried to go backward to 7.0 release stuff to live what I failed to live with the rest of you (since my applications were so complex and they worked [if it ain't broke...] and I was working in PHP on the web so much) during the initial days of migration. (Now my clients feel they must upgrade since 6 won't be supported soon.) Any best versions of this explanation of the whole multiple-window / commit mechanism? Any best book (the Moyer book table of contents looked promising)? Any recommendations? I remember exclaiming often when I was fixing bugs in pre-7 applications that "ExitRecord/Request" was the "Chicken Soup of FIleMaker" -- it seems as though they have made that whole area more robust, yet with some attending unintended side-effects (probably to my kludgy workarounds). So notwithstanding what seems like good advice, I would like to understand the why's and wherefor's so that I can understand and predict behavior as I debug. It was like when someone said "you'll have a better lawn if you mow your lawn with Golf shoes on", and it seemed like silly if not superstitious advice. Then when someone that knew landscaping explained that you will aerate your lawn as you mow then it made sense -- he even told me of specific shoes you can buy that do that better than Golf shoes. Any reading recommendations? Even if you can recommend searching this list's archive for a particular thread way back when for 7.0? Thanks in advance, Brad On 1/27/07, Roger Wilkerson <[EMAIL PROTECTED]> wrote:
At 09:42 AM 1-27-2007 +0000 Rowland Carson wrote: Roger - you need to move the cursor out of the fields in the portal before you go to the layout in the other file. If you don't it thinks there is still a pending edit. Yes this did fix the "record cannot be modified error" By moving the cursor out of the fields in the portal(clicking anywhere on the layout outside the portal). I then can GTRR and continue editing. I think a commit record step before you GTRR would also do the trick. I also discovered another problem. I had/have the button set up to Go To Related Record. This works fine. Someone had mentioned that it was not a good idea to use a button to directly run a script step. That is was best to create a script that will GTRR. Then have the button run the script. This way I could also have the commit step prior to the GTRR command and it would take care of the initial problem. I tried this. When the button was set to run a script, nothing would happen. I would not be taken to the related record. The screen would "kind of refresh" and remain on the main layout with portal. I then just created a script that simply ran the GTRR script step. Had the button run the script. Again, nothing happened. The only difference between the two methods is the button action. In the successful event, the button simply GTRR. When I have the button run a script to GTRR, it does nothing. Any suggestions? Roger ------------------------------------------------- Tune into my station at: http://www.live365.com/stations/333303?play <http://www.live365.com/stations/333303?play%C2%A0> WAR HAS NEVER SOLVED ANYTHING, except ending slavery, facism, communism, Nazism.... Practice safe eating - always use condiments If we are what we eat, then I'm easy, fast, and cheap Without geometry, life is pointless.
-- Sincerely, Brad
