a) a description or screen shot (from manage database) of the tables and relationships that store the data you want to use for your report.
b) at least a general sketch of the report format that you are trying to create and specifically how you are trying to use a portal or portals in that report.
If there is only one portal that you need for your report, there is a very nice alternative to portals that can possibly be set up for your report.
Ok. The relationships at the moment are as follows:
Clients::ClientID = Applications::ClientIDFK
Applications::AppID = Services::AppIDFK
I have attached a quick idea of the report layout I was hoping to achieve. The other way to do it is first list all the Applications for a client as in the sample then list all the services under them and I could reference the AppIDFK so we know which application its associated to when reading it, It doesn't HAVE to be application 1 then all associated services, application 2, all associated services, etc. Although that would be ideal. Mainly I just need to maximise the space on a report for printing so that's why I'm trying to use the slide up feature as some will have very little info and other loads.
The good news is that there is a simple list view report method that will work for you that does not use portals. It works because your relationships forma a "one to many" single "chain" of relationships:
If there were branches to this chain or they weren't all one to many as you read from left to right, this wouldn't work.
Create a list view layout based on Services.
Put fields from Clients into the header, footer or a grand summary layout part
Put fields from applications into a sub summary layout part (When sorted by appIDFK)
Put services into the body. (size the body to be a narrow row of information)
Perform a find for all Services records, specifying a specific Client ID in Clients::ClientID. This will find all services records linked to that Client. Sort your records by appIDFK in order to make the sub summary layout parts visible.
There is one possible limitation to this report that may keep it from working for you. This approach assumes that there will be at least one record in services linked to every application record for this client. If you have any application records with no services specified, they won't appear in this report.