Portal and If Statements?

[Hawaii80]

Gonna do my best to explain this...

 

I have 1 table, (call it TableA) for owners which one enters a description of debits, their amounts and check number when rents are received in from tenants. It is necessary to take funds from the owners distribution for bills we may have to pay for them prior to sending them their net. Thus the fields debit, credit and check number.

 

I also have 2nd table, (call it tableB) for other expenses for owners which also has debit, credit, and check fields. But must remain a separate table from the other, so can't combine the two. Not an issue there, just letting you know.

 

Then, on a 3rd table called properties, I have a portal showing the owners expenses, (TableB), no problem showing this data at all. But, I was wondering if there was a way to have the portal combine both tables A and B above, and I don't mean in separate columns rather 1 line item below the the other. I know I could have 2 portals for each table right next to each other if I want, but the goal is to have the debits/credits on 1 line each below the other .

 

Example - say I enter a description, debit/credit on TableB; voila it shows in the portal on the properties table

 

But let's say I also enter on TableA a description, debit/credit record also, is there a way to have this data also show on the next line of this same portal from where TableB is displaying data? Or do I have no choice but to have 2 separate portals, or include them as separate columns within the portal?

 

I hope this make sense.

[Weetbicks]

Are the records in TableA related in some way to the records in TableB . I'm assumign they are since your goal is to show a record from A below a record from B (which I assume they are somehow connected??)

 

If there is a relationship between them, make a calc on either A (or B), which contains the content of the record in A, PLUS a return character "¶" followed by information from the related B record. Then just stick the calc in the portal for table A. The related info from B thus appears below A (but on the same portal line, which I think would be fine?)

 

Or am I incorect in this assumption? Are tableA purely debits and tableB purely credits? and you want it to look like a ledger style in order of say date?

[Hawaii80]

Hi Weetbix,

 

The properties table which has the portal, is related to TableA and also properties table is related to TableB.

 

TableA and TableB both have debit/credit and I do want to look within the portal ledger style in order of date descending and hopefully showing both Tables A/B within the same portal. Basically the goal is if there are debits/credits on A and/or B show them within the same portal, (ledger) vs. 2 separate portals.

[Hawaii80]

If there is a relationship between them, make a calc on either A (or B), which contains the content of the record in A, PLUS a return character "¶" followed by information from the related B record. Then just stick the calc in the portal for table A. The related info from B thus appears below A (but on the same portal line, which I think would be fine?)

 

Since properties is the table related to A and B could I just calc on properties?

[Hawaii80]

Then just stick the calc in the portal for table A. The related info from B thus appears below A (but on the same portal line, which I think would be fine?)

 

Also to answer the above question, it would be best if Table A and Table B records appear as though they are separate entries within the portal, rather than both on the same portal row. I may be asking for too much, but thought I'd see if something like this was possible.

[Weetbicks]

If it was purely for a report I'd tell you to import records from A and B into a temporary reporting table C and run the report off that. Since you want to display them on a layout, thats impossible using a portal.

 

Unless you manage the creation of records in A & B via script. Create your temporary table C, then everytime you create a record in A or B, create a record in C, link the record in C to either A or B. Then your portal can show records from C. Since records in C are linked to A or B you can easily show records from both A&B in the same portal (based on C). See?