Best strategy

While hazzling around with this new tool and being "surprised" from time to time, for instance if PHPR adds obviously invalid arguments to SQL-statements (AND 'key=''', for instance, causing SQL-syntax errors all the time - or adding new columns to my db-tables ("active" and "generatedbyPHPR"-cols in user-registration)) I'm currently wondering which route to take:

1. create an app with all standard-settings/features and then remove the unwanted ones ("add", "search" functionality and layouts in my case)
   
   or
   
2. create a "minimal app" with anything probably unneccessary disabled/deactivated and adding the customized features afterwards.
   
   ?
   
   I took the second approach, but most of the stuff didn't work out well:
   

• I set a header(Location: editview.php) event script but ended on a blank page
  
• I removed the "add" functionality, but even if there is a related record in the table (either created directly in the db or using a PHPR-event) it is not offered (or listed) for editing.
  This seems to be a not very intuitive cross-effect of keys/relations/layouts/events/scripts and somewhat hiddeen "PHPR-intelligence" .. well: I have no real clue on how to get along with that stuff.
  I would like to hear of your beginner's experiences - and expert's advice, of course <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=question&id=7907&image=1&table=forumtopics' class='bbc_emoticon' alt=':rolleyes:' /> !
  tia,
  
  paul