Large Forms Design Using MS Access 2010 - ms-access

i am trying to make a form design in Ms Access 2010, for that firstly entered fields into Access Table. Then try to
Create->Form Wizard
Actually my table is too big, so form wizaed is not creating the form . Also i want divide this form into separate parts. I tried "Tabs". But My problem is that when i take the printout of form i want actually get the full form in one print. If i use Tab, that is not possible. How can i solve this problem.
Thank You All

You can use tabs if this is working for you and also create a report that includes all the fields that you need to print out. This report can be activated by a Print button.

Related

Combining two reports to one in Access 2013

I've two reports in my DB that I want to combine. Both these reports have various fields populated from preceding steps and a hyperlink that opens a form for further processing. The form auto-populates some of the fields using the data from the report with
=[Reports].[MyReport].[LineItemID]
I'm using a 3rd unbound form to put the 2 reports on a single screen (using simple drag and drop). The hyperlinks on both the reports don't read data from respective reports anymore. I tried using
=[Reports].[MyReport1].[LineItemID] to read from individual reports and also
=[Reports].[CombinedReport].[LineItemID] to read from the combined report but doesn't seem to be working.
Any pointers on this would be very helpful.
Thanks,
When you placed the two reports into the unbound report, you also created a control of type subform/subreport for each in the unbound report.
This you have to respect in your reference. You will have to check and use the names of these controls.
So if the control for the first report would have been named MySubControl1 this is your full reference:
=[Reports].[MyReport1].[MySubControl1].[Report].[LineItemID]
The extra .[Report] is included because you now also need to explicitly reference the content of the control (which in this case is a report) to actually have a reference to your embedded report object, and be able to reference the required LineItemID control within it.

How can design view of a form be disabled by vba code and still display the contents of form correctly?

I want to disable the design view of my from. Therefore, I saved my database as accde,doing so disables the design mode.However, doesnt load the form correctly.It isn't diplaying the information in drop down boxes as in the accdb file. It is displaying the drop down boxes where I have created a value list and not displaying the data in drop down boxes which have been extracted from a table.
Also, is there any way to hide my tables as well from the users.
Thanks Please assist
The VBA code needs to be compiled before saving the file into accde. Also, make sure the trusted location settins is turned on where the database file has been saved.

MS Access: Reports referencing other reports

I have several MS Access 2010 Reports that contain controls that reference other controls on other Reports. So, for example, if report1 has a text box called report1_textBox, and this text box gets its value from a text box on report0 called report0_textBox, then I set the Control Source property of report1_textBox to:
= [Reports]![report0]![report0_textBox]
I created a Form that the user can use to select Reports to open, and when the user selects a Report that depends on other Reports, my code opens those Reports before opening the selected Report. This works fine in some instances, but in other instances I get some strange behavior.
Going back to the example above, I encounter situations where even if I open report0, then open report1, the text box report1_textBox displays #Error as if report0 is closed or does not exist. But if I then just click on report0 and change its view then change it back, then go back to report1 and scroll a little, the text box report1_textBox "magically" changes from #Error to the proper value. I tried hitting the "Refresh All" button after opening the reports, and it does not update the text box.
Does anyone know of a way to fix this or at least work around it?
Thank you!
(Adding: Ideally, I do not want to open multiple reports like I'm doing now. If the user wants to view a report, I would like to only open that report, but from what I understand, if the selected report needs data from another report, that other report needs to be open. I can ultimately solve this by writing VBA code to execute queries, but I would like to avoid this, especially since I already have the data I need - it's just on another report. Does anyone know if it is possible to realize this ideal situation? Thanks!)
I would suggest going with VBA code for this.
Your question, actually, contains an answer (partial) - if you need data from another report that report must be opened first. However, the following code might help you somewhat.
You can open report(s) as hidden:
...
DoCmd.OpenReport "report0", acViewReport, , , acHidden
...
But again, I would recommend to write VBA code to pull the data using either existing queries from other reports or create new ones [queries].

Blank forms displays in MS Access

I just converted my MS Access database from 2000 to 2003 format and then created an executable (.mde) file. The executable works fine, but on one form the screen is blank in form view, even though all of the contols show up in design view. What am I doing wrong?
Check to see if the query populating the form is returning any rows back.
I figured it out. I adventently turned on the filter. When I turned it off, the form displays data again.

First page of MS Access Report does not seem to call On Page Event

I have coded a MS Access 2000 report that displays a calendar with one month per page and projects added to particular days. The only data in the underlying record source is a list of months. The structure is created via the On Page event, which also reads in other data.
When this report is opened, I've noticed that the On Page event does not seem to be triggered for the first page. (I attribute this to the fact that On Page in reports is activated when a page is cached rather than when a page is displayed, such as On Current for Access forms.)
When the report is displayed my work around is to use the On Activate event to force the On Page subroutine to run even though that event has not been called. However when the report is exported it does not trigger the On Activate event and the first page of the export is in one of two formats:
1) if the report was open in Access (ie On Activate had been triggered previously) the first page is identical to either the page after the one being displayed or the last page, except with the correct month (which comes from the underlying record source)
2) if the report was not open in Access the first page contains just the structure within the report design view (ie lots of empty boxes)
My best workaround is to force a (otherwise pointless) cover page to ensure the first page contains nothing that needs code to run, but this is far from ideal. Can I force the code to run for the first page of an export? Or maybe I'm misunderstanding how On Page works and I need to restructure my code? (I've also noticed that On Page seems to run twice for the last page).
I would recommend restructuring your code so that you build your data in one query, multiple queries, or in VBA, and then open the report with the new datasource. I might still have Access 2000 at home to check, but at work I can test both 2003 and 2007, and in both versions, the OnPage event fired before each page was displayed. If you are experiencing different behavior, I suspect it's because Access isn't sure how to handle what you are asking it to do.
Typically a report like the one you are describing would be designed the other way around: the datasource for the report would contain all the project information. Is there something about the data you're trying to display that prevents you from building a query that would contain all of it?
Have you considered the Format event for the various sections, especially the Detail section? Format or Print are a more usual events for manipulating reports.