Sorry for the late replies. I didn't have access to a computer for a week. ItsMe I don't really understand the subform approach so could you go into a bit more detail please, I know how to do the steps you said but it seems like details are missing between each step. Thank you for the tips June7 and ItsMe I will try to make the form smaller.
Sorry for the late replies. I didn't have access to a computer for a week. ItsMe I don't really understand the subform approach so could you go into a bit more detail please, I know how to do the steps you said but it seems like details are missing between each step. Thank you for the tips June7 and ItsMe I will try to make the form smaller.
The only thing I think I can add is how you would reference a subform from a main form. In your case, you are closing the whole thing, Mainform and Subform. So the close comand for that would be Docmd.Close
If, within this close control's click event, you have additional lines of code that reference the subform, you will need to bring the reference back to the Mainform for the Docmd.Close line to function correctly.
A couple of examples:
Docmd.Close acForm "MainFormName"
or
Forms!MainFormName.SetFocus
DoCmad.Close
This can get confusing. There is a sample DB I uploaded that has examples of using controls on a mainform to manage a subform's properties. You may want to look at it for reference.
https://www.accessforums.net/sample-...tml#post191005
.
Don't think you ever directly answered my question in post 5 about whether are not this form has subforms on it. If you don't understand what ItsMe said about using subforms then I guess that does answer.
If you don't already have subforms, I am not sure adding a level of complication induced by their use is really needed. If the rearrangement of controls resolved the horizontal scroll, is there still an issue?
Perhaps organizing controls on a tab control as already suggested is all that is needed.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
June7 is correct. Unless you are going after a Data Sheet view effect, the subform is more work and less intuitive for the user. You chose a continuous form for a reason.
Take a couple steps back and ask yourself why grouping your controls onto tabs is not an option. After going through the steps of the subform you will most likely appreciate the tabs approach.
No there isn't an issue any more but I just wanted to see any other ways there could be to get around the problem because I don't think rearranging the controls is visually appealing, also others may want to find out other ways to do this.
Basically there is a form which users use to enter search criteria. When the criteria has been entered a query runs and and returns the results that meet there criteria in a continuous form. A user then uses the record selector in the continuous form to select a record and a form opens with the details that specific record. Users can edit the record from this screen.
The problem was that in the continuous form thee were quite a lot of fields so users would have to scroll horizontally to see all of them. I don't see how tabs would work in the continuous form but I could see how it would work in the form that opens to the selected record. Only way I can see it is by having the continuous form show each record in tabs, but I'm not even sure if that's possible?
If the form that opens to the selected record is a sub form then yes I have a sub form.
Thanks again for the replies.