At 05:12 PM 1-27-2007 +0000 Tom Elliott wrote:
>Roger,
>
>If your button is in the portal row, then when it's set to run your  
>script, the Commit record steps exits the portal row so the GTTR  
>makes no sense (whereas when your button simply executes the GTTR  
>script step it'll work because you have manually committed the record  
>and effectively re-enterd the portal row by clicking the button)

Ok, seems logical.  What I do not understand is why if the button set up 
is:GTRR, then all is well.  It works.  Goes to layout and record it is supposed 
to.

However, if the button set up is to "perform script" and the script is a simple 
one line of GTRR with the same layout and table identified in the button action 
above, nothing happens.

Again, the only difference is the button set up:one is direct GTRR and the 
other runs a script that GTRR.

>If the button is outside the portal .... well what is tour GTTR  
>referencing?
>
>cheers
>
>Tom
>
>
>On 27 Jan 2007, at 16:24, Roger Wilkerson 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
>>
>>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.
>
>
>-- 
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.432 / Virus Database: 268.17.12/653 - Release Date: 1/26/2007 
>11:11 AM

-------------------------------------------------
Tune into my station at: http://www.live365.com/stations/333303?play  

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. 

Reply via email to