June 17, 200520 yr I have just created a database for the school I teach at which displays, among other things, a student's misdemeanours through a portal. Each portal row has a preview/print button to either preview and/or print the contents of that portal row in bigger detail in a separate layout. Clicking this button on some of the portal rows correctly displays the field contents of that row in the new layout while clicking the button on other portal rows causes FM to display the first record of the database and then exit from FM7 when a Continue button is pressed (which pops up when the portal row's button is clicked). The stange thing is that I use the same setup to view student's non-submission of work, and the setup has always worked correctly. I've tried unsuccessfully to find the cause of the problem, but am at a loss as to working out what is causing the current problem. I would appreciate your help! Frank
June 17, 200520 yr I would check the GTRR to make sure that it is not set to show only related records. I would make sure that the button is completely inside the portal row. I would make a copy of the script and use the copy with button. I would then delete script steps until it no longer produces the continue button. I would make a new layout with the portal and the button, do not copy from the old layout.
June 18, 200520 yr Author Dear RalphL Thanks for your tips! Given that the error was only occurring with certain records, I felt that the error lied not in the script (as it worked most of the times) but with the original layout that held the records. (More specifically, the records on the layout themselves because deleting the record on the portal row that caused the problem then re-entering the record caused the problem to not re-appear). I created a new layout, deleted the old layout, and everything is OK at this stage. My only concern was that in deleting the old layout, you would be deleting the records as well..but this didn't happen). Again, thanks from the Land Downunder! Frank
Create an account or sign in to comment