Restore "Continuous" form behavior in MS Access after subform is added - forms

I created an Organization form in Access 2007 that could be used to display any record in the Organization table by clicking the navigation buttons that appear at the bottom of the form when it is in "Form View". Next, I created a subform within the Organization form to display records from another table that have a foreign key from the Organization table.
Now the "Default View" property of the Organization form has been automatically set to "Single Form" and when I try to set it to "Continuous Forms" I get the following message:
You can't view a form as a continuous form if it contains a subform, an ActiveX control, or a bound chart.
Set the DefaultView property of the form to Single Form, Datasheet,
PivotTable, or PivotChart.
Furthermore, I am unable to use the form to view any records other than the first record in the Organization table. How can display other records from the Organization table in my form using record IDs?

While investigating this problem, I discovered that Microsoft's own Northwind Traders Sample Database contains at least one form with subforms that exhibited the behavior I wanted, even in the "Single Form" view. This suggested that the subform was not the cause of the problem.
In trying to reproduce the affect accomplished in the sample database, I recreated my form and re-added elements too it one-by-one, testing the navigation at each step. I was able to view different records via the "Form View" navigation button until I added controls from a table other than Organization that weren't contained within a subform.
So there you have it; switching between a form's source records via the navigation controls in "Form View" does not work when the master form contains records from more than one table.

Related

Requery a subform within a tab control

I have several controls on this form in addition to a tab control with 3 separate pages. I want the subform(s) within each page to requery when a value is selected on the page above.
So for the purposes of explaining this..
I have an event On_Click() on a field called Address_ID. It's meant to take tha value of that ID in addition to two other IDs, Cust_ID and Location_ID, and requery the subform Order_Sub within the Orders page.
I've named the tab control pretty blandly, just tabCtl.
So far I've tried every way imaginable to reference the subform, but to no avail.
Forms!Record_Details!Orders!Orders_Sub.Requery
That doesn't work, but I assume that it should. What gives?
Steve
You do not need to reference the tab control in your code. Just reference and requery the subform itself
Forms.Record_Details.Form.Orders_Sub.Requery

How do I create a subform that shows query results of a search on the parent form?

I'm quite new to MS Access but understand basic dvl concepts. I have a form (SalesOrder) where I can create sales order info. Creating a new sales order populates more than one table.
I'd like to have a two search buttons on the bottom of the form that will display the results of a query (search by customer name or order id). The results of the query need to be displayed in a subform, and once I click on the selected row, it should populate the master form fields with read-only data (i'll have an edit button to change to writable).
Do I simply link a query to the subform? If so, how do I do that? and how do get the event in the main form (the search button click event) to trigger action in the subform?
thanks in advance.
jeff

View details control on ax 2012 form

I would like to bring view details button in my form when right clicked on my form view details should be shown like in standard any form for example when we right click on item number field on the form we have view details option when clicked that opens the details form of that item.
I tried using the normal right click method but could not succeed, please help me how to bring the view details functionality in my custom form.
To have the "View details" standard context menu, the following must be true:
The foreign key (FK) must have a relation defined on the table of the key
The table pointed to by the FK must have a form
The form must have a display menu item
The menu item must have the same name as the table or the FormRef property must be set
The menu item must have security set up, and the user must have read access (or better)
Running the Best Practice check will usually spot the errors.
This blog entry explains it nicely.
You have to create Display Menu Item with the selected form.
Then you can set newly created menu item for the FormRef property of the Table.

MSAccess - subForms of the same table

Here's my scenario:
I have a a main table, Projects, with a o2m relationship to a second table Changes. This second table is quite wide so I would like to be able to segment the information across several subforms on different tabs.
I've created a main form, the tabs and the subforms on each tab and the presentation is fine. The problem comes when I create a new record. On the first tab (containing subform1), I create a new record and fill in some values. When I click on the second tab (subform2), the new record is not there. My question is how can I keep the different subforms all in sync?
I've tried to do a Requery of subform 2 using the OnClick event on the second tab but to no avail. I could be just doing that incorrectly.
Any ideas please?
Thanks,
Jon C

How to shift a record from one view to another view through workflow in crm 2011 on-premise

How do I shift a record from one view to another view that is a custom view through workflow?
I want a functionality such that when a record is processed and saved it should shift from "Active" view to another view named as "Processed" through workflow. Right now it is giving me the option to shift it from Active to Inactive on "Change Record Status."
is this even possible? or is there a workaround?
Your custom view "Processed" shows the records based on certain conditions (for example a view can show the records recently created or where a field contains a certain value).
So inside the workflow you need to update the fields that make a record belongs to the custom view "Processed".