![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Helpfull Harry advises not to print portals, I'd be interested to know why. |
|
If I have 2 tables, one Customers and one Items. Related by unique customer number. I can display and enter related records in a portal and even print the portal to look like an invoice or whatever. How do I display/print the same thing without a portal? Do I have to FIND the related records in the Items table first so as to only see the related ones without a portal? There is likely a simple answer but it just escapes me as a beginner with RELATED tables although an FM user for many years. |
)
#3
| |||
| |||
|
|
In article <9kg156h34dtj0gdrgouhcru49j7cbqu9v8 (AT) 4ax (DOT) com>, John G greentest (AT) ozemail (DOT) com.au> wrote: Helpfull Harry advises not to print portals, I'd be interested to know why. Portals weren't designed for printing and can, but not always, cause strange problems with the printout (for example sliding not working properly). It's a little like using Repeating Fields instead of a Related Table ... it can be done, but is usually best to do it the proper way. Thanks, even normal printing gets confused sometimes and prints only |
|
If I have 2 tables, one Customers and one Items. Related by unique customer number. I can display and enter related records in a portal and even print the portal to look like an invoice or whatever. How do I display/print the same thing without a portal? Do I have to FIND the related records in the Items table first so as to only see the related ones without a portal? There is likely a simple answer but it just escapes me as a beginner with RELATED tables although an FM user for many years. You've got the idea. Basically you do perform a Find or use the Go To Related Records command to get only the related records in the other Table and print the report from that Table using a normal Body Part on the Layout. You can have a Relationship link going back the other way to retrieve the customer's name and address to be printed in a Header. Another way can be to use a Script or Calculation Field to bring the related data into the Customers Table. Helpfull Harry ) |
#4
| |||
| |||
|
|
On Thu, 29 Jul 2010 14:05:49 +1200, your.n... (AT) isp (DOT) com (Your Name) wrote: In article <9kg156h34dtj0gdrgouhcru49j7cbqu... (AT) 4ax (DOT) com>, John G greent... (AT) ozemail (DOT) com.au> wrote: Helpfull Harry advises not to print portals, I'd be interested to know why. Portals weren't designed for printing and can, but not always, cause strange problems with the printout (for example sliding not working properly). It's a little like using Repeating Fields instead of a Related Table ... it can be done, but is usually best to do it the proper way. Thanks, even normal printing gets confused sometimes and prints only the top or bottom of a line. If I have 2 tables, one Customers and one Items. Related by unique customer number. I can display and enter related records in a portal and even print the portal to look like an invoice or whatever. How do I display/print the same thing without a portal? Do I have to FIND the *related records in the Items table first so as to only see the related ones without a portal? There is likely a simple answer but it just escapes me as a beginner with RELATED tables although an FM user for many years. You've got the idea. Basically you do perform a Find or use the Go To Related Records command to get only the related records in the other Table and print the report from that Table using a normal Body Part on the Layout. You can have a Relationship link going back the other way to retrieve the customer's name and address to be printed in a Header. Another way can be to use a Script or Calculation Field to bring the related data into the Customers Table. Helpfull Harry * )Thanks for that I won't be looking for something that doesn't exist. John G. |
![]() |
| Thread Tools | |
| Display Modes | |
| |