I recently amended a db from an old Lynda course, controlling shore excursions for river cruise ships. For my limited expertise (I am still a rookie at the very best) the construction is somewhat complex as there is many vessels, different routes, different charterers and consequently different shore excursion programs and prices. In some cases the shore excursion program of different vessels and operators is similar but not the same and so on.
I have 7 different tables partly related (pls see graph attached):
For every journey ::customers and ::trip are assigned a tour code and date (“tour code” is not unique as journeys repeat themselves during the season, “Tour Code” in conjunction with “Date” is unique)
Every tour operator/vessel has many trips on every journey. All table occurences and fields are uniquely defined by unique id.
Now I want to create an opening layout reflecting all relevant cruise information such as passenger list from ::customer and ::trip (shore excursions) for the specific journey, as well as other information in text fields.
But I seem to be unable to get the right relationship and layout setups together. I tried all possible relations and layout setup combination but nothing worked so far.
On the same layout I was able to either retrieve the passenger list from ::customer for each journey or the offered shore excursion (trip) list from ::trip but not both together on one layout.
What is it, I am doing wrong? Any ideas are appreciated
Hi All, I have a database where the relationship between the Quotes table and the QuoteItems table is set up such that if a record is deleted in the Quotes table, the related records in the QuoteItems table are also deleted. I have now been shown an instance on one Customer where there are four Quotes missing from the Quotes table but all the QuoteItems are still in the QuoteItems table. How can this be done, I am unable to recreate a circumstance where I can delete a quote and leave the quoteitems in place.
Any help appreciated
i have 3 Tables Property , Units , Tenant.
Each property has many units , Each unit has one tenant active but may have many inactive tenants from previous years.
All working fine BUT.....
i would need to show a table in the property layout of the units and each one only with its active tenant.
The portal is based on the units table.
However the tenant just show up the tenant that was first input to the unit.
My question is , how could i get that only the active tenant should show to the unit?
i would really appreciate it someone could guide me on this.
I'm sure there is a simple solution to this problem, but I can't seem to figure it out!
I have a custom app that allows the user to write letters amongst other things.
Each patient is linked to a GP and a Consultant, when writing a letter to a patient there is the option to CC both the linked GP and Consultant. However, occasionally another GP or Consultant might need to be CC'd in the letter (in addition to the ones already linked to the patient). So I would need the address of this additional consultant/GP to also be CC'd in the letter. For the life of me I can't work out a simple way to do this.
Does anyone have any suggestions?
Thanks in advance.
I have a filterable portal (1) displaying contact names from a staff table. I need to click on a contact to add them to a separate portal of invitees (portal 2) on the same layout (Events) . I then need the original portal to either hide (or in some other way denote) the people already added to the second portal. In other words, it needs to be clear that a person already invited can't be invited again.
The layout is from the table: Events
Portal 1 is showing records from Staff (filterable via a global search field)
Portal 2 is showing records from EventInvitees
I need Portal 1 to only filter through those staff who haven't been invited yet.
Any help would be gratefully received.
I am struggling around using 'conditional formatting', 'hiding when…' options and non-matching field relationships!!
Thanks in advance!
Who Viewed the Topic1 member has viewed this topic:Toni