Jump to content

IanPDT

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About IanPDT

  • Rank
    novice
  • Birthday 12/05/1951
  1. OK Soren, with your help i've cracked the problem. Your script works great when the portal row only conatins one field - in fact I think it can be simplified - see my adaptation in attachment. For my portal, with multiple fields I have found a different solution - see pickerscript.jpg I doubt if I would have got there without your ideas so many thanks. Ian Jumpingbeans3.zip
  2. Many thanks Soren - will get to work adapting this and let you know how I get on.
  3. What I mean is some portals may have 5 records, some 6 some 10 etc. If they were all the same then your solution works fine - as you say by altering the div value.
  4. OK, I've got the hang of it but have one more complexity which upsets line 3 of script. That is not all portals will have same number of records! Div function does not work with some portals having more than 4 records. Any ideas?
  5. Hi Soren, think I've got it worked out now - don't worry about adding comments. this has given me a real start on solving problem, many thanks.
  6. Many thanks Soren - this looks as though it will do the job. I've experimented a little and can see how some of it is done - I have added a fourth portal but I don't really understand all the steps in your script. Any chance of you adding some comments to it? Thanks, Ian
  7. OK in my real there are many fields to display so a single portal can only display 40 rows - to the bottom of the layout screen. Yes I do need to see all the records in the file but given that there will be several portals across I need to jump to the right record on the layout - hence the "picker". The number of records will vary but I can predict a maximum so set up enough portal space for this (there will be multiple instances of this database to author multiple flow diagrams sourcing data from related tables) Also as a flow develops, the portals will be shifted around in layout mode
  8. Hi, Why not view separate companies in a portal? Make a global field g_company and a self-join between that field and your companyID field. The portal onto the company data will then only show values currently related to the value in g_company. You can populate the g_company field with a value list made up of all the values in your companyID field so enabling you to switch companies easily. This would work in a networked environmnet and you could restrict access by pre-setting g_company apologies if I've missed the point.
  9. I've attached an .fp7 file to show you what I'm trying to do. The data in my portals is much more complex -hence the size of the portal. Basically imagine it like a flow diagram - one record is linked to another via the order/jump values. Try the "picker" and you will see what I mean about being able to jump to first portal but no any other. thanks for thinking about this, Ian portaltest.zip
  10. OK tried the global field in portal idea (g_portal) - thought I may be able to trap the error when you try to go to a portal row not in current portal then script to go to next g_portal field etc until the row is found. Snag is, there is no error to trap! With error capture on the dialogues still appear and get(LastError) doesn't return anything!
  11. No, for various reasons I need to display all the data at once, not have some hidden in a scrolling portal.
  12. On a layout I have a portal displaying related records. There are several fields in the portal which means that I can only display so many records - no problem I just have multiple portals for the same relationship using the "Initial row", "Number of rows" parameters to have side by side portals display the data. My problem is jumping to specific portal rows in the multiple instances of the same portal. Let's suppose PortalA contains records 1-20 and PortalB contains 21-40. If the focus is in portalB and you run a script to go to portal row the dialogue shows "Go to Record X out of 40
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.