Ticket purchase application has the following elements (to name a few):
CustomersQ = Select query using table Customers and Membership joined by CustID.
OrdersQ = Select query using tables Orders, Performance, Prices and Customers joined by
various fields such as CustID, PerfID, PriceClass, etc. A complex query.
Form Customers uses record source CustomersQ. The ordering procedure goes like this:
Select customer, select performance, click on "Order" button which creates new record in Orders table. Then open form OrderPerf using record source OrdersQ for specific record just added. Click on tickets, click on seats, click on payment, print tickets, close OrderPerf form
which returns to Customers form. No problem. Working like this for years.
Decided to add table Membership to OrdersQ to extract a couple of fields for order checking.
Table Membership is linked to table Customers by CustID as in the CustomerQ query. I also tried replacing the Customer:Membership tables with the query CustomersQ, but the result
in both cases was the following:
Form Customers is using record source CustomersQ. The ordering procedure goes like this:
Select customer, select performance, click on "Order" button which creates new record in Orders table. Then open form OrderPerf using record source OrdersQ for specific record just added. Click on tickets and - "RTE 2448 You cannot assign a value to this object".
This also happens if another order form is opened from form Customers such as "Make a Donation" which also uses the OrdersQ as the source record. Click on a control and BOOM!
So it would appear that the revised OrdersQ is the culprit. But why?
Remove Membership table from OrdersQ and we're back to normal.
What am I doing incorrectly in changing the OrdersQ linked tables?