Form Data to Report Data
in [Reports]
|
Prev: printing snp / rtf files
Next: Report Hangs
From: Rob G on 29 Jan 2006 13:55 I am sure I am making a newbie mistake, but I think I have a legitamate problem getting data from a form to a report. I have a very complex UNBOUND access form and it has several command buttons that spawn a few different reports. I know that generally reports have to open a form to get data, but in my case, all the work is done by THE FORM and its module. As far as I can tell, the only way to get data from the form/module is to write the data to the database and then open the report bound to the database. Someone please tell me this is too much work and there is an easier way. I have tried to access the form data from the report, but the data in the form seems to be out of scope for the report. Help!
From: John Spencer on 29 Jan 2006 14:55 A) Is the form open? It must be for this to work. B) How are you attempting to refer to the form's controls? Standard syntax is [Forms]![YourFormName]![TheControlName] That should return the value in the control of the open form. C) You mention getting data from the form's module. Do you mean that you are populating variables and want the report or an underlying query to see those variables? If so, the easiest method is to add some controls to THE FORM and set the value of the controls to the value of the variables. You can set the control's visible property to false if you don't want them visible. If none of the above apply, can you give a little more detail on what you are doing. Rob G wrote: > > I am sure I am making a newbie mistake, but I think I have a legitamate > problem getting data from a form to a report. > > I have a very complex UNBOUND access form and it has several command buttons > that spawn a few different reports. I know that generally reports have to > open a form to get data, but in my case, all the work is done by THE FORM and > its module. > > As far as I can tell, the only way to get data from the form/module is to > write the data to the database and then open the report bound to the database. > > Someone please tell me this is too much work and there is an easier way. I > have tried to access the form data from the report, but the data in the form > seems to be out of scope for the report. > > Help!
From: Marshall Barton on 29 Jan 2006 15:14 Rob G wrote: >I am sure I am making a newbie mistake, but I think I have a legitamate >problem getting data from a form to a report. > >I have a very complex UNBOUND access form and it has several command buttons >that spawn a few different reports. I know that generally reports have to >open a form to get data, but in my case, all the work is done by THE FORM and >its module. > >As far as I can tell, the only way to get data from the form/module is to >write the data to the database and then open the report bound to the database. > >Someone please tell me this is too much work and there is an easier way. I >have tried to access the form data from the report, but the data in the form >seems to be out of scope for the report. It's certainly more in keeping with a database system to put the data in a table. But Access is a very versatile set of tools and an unbound report is not unheard of. If the report can live within the design limits of 200" high (using a bunch of sections), then you can easily lay it out using text boxes with references to the form's controls: =Forms!theform.controlname If that's the kind of thing you tried, then you'll have to post more details before we can figure out what your problem is. Things get trickier as you try to expand on this basic approach. -- Marsh MVP [MS Access]
From: Rob G on 30 Jan 2006 05:50 Thank you both for your replies. The form is still open and I have tried to set up a simple example using one text box from the form as a prototype for this problem. Private Sub Detail_Format(Cancel As Integer, FormatCount As Integer) Me.LabelTEST = Forms!MyForm.MyName Me.LabelTEST = Forms!MyForm!MyName End Sub Both for lines of code yield the dreaded "Run-time error '-2147352567 (80020009)': The value you entered isn't valid for this field." John's question in part C) All the form's business logic and data come from the module. The data that the end user adds to the form gets copied and manipulated in the module causing other values to change and ultimately some sections of the form get refreshed. The the user is done putting in the data, they choose a report as a view of that data. The goal is to have them print that report and then I'll write the appropriate data to the database from within the module and close the form. Sometimes a user has to see their work before they accept the data and want to commit it to the database. I hope I answered your questions and tried to keep the focus on a simple example to which we can conquer the larger task. Thank you. "Marshall Barton" wrote: > Rob G wrote: > > >I am sure I am making a newbie mistake, but I think I have a legitamate > >problem getting data from a form to a report. > > > >I have a very complex UNBOUND access form and it has several command buttons > >that spawn a few different reports. I know that generally reports have to > >open a form to get data, but in my case, all the work is done by THE FORM and > >its module. > > > >As far as I can tell, the only way to get data from the form/module is to > >write the data to the database and then open the report bound to the database. > > > >Someone please tell me this is too much work and there is an easier way. I > >have tried to access the form data from the report, but the data in the form > >seems to be out of scope for the report. > > > It's certainly more in keeping with a database system to put > the data in a table. But Access is a very versatile set of > tools and an unbound report is not unheard of. > > If the report can live within the design limits of 200" high > (using a bunch of sections), then you can easily lay it out > using text boxes with references to the form's controls: > =Forms!theform.controlname > If that's the kind of thing you tried, then you'll have to > post more details before we can figure out what your problem > is. > > Things get trickier as you try to expand on this basic > approach. > > -- > Marsh > MVP [MS Access] >
From: John Spencer on 30 Jan 2006 07:53
Is LabelTest a label control? If so, you can't assign a value to a label. You can assign a value to the caption of the label. Me.LabelTEST.Caption=Forms!MyForm!MyName Just checking. I note that your example does not use the [] around the reference to the form control. I know this is not required with the sample names since you did not have any spaces or other special characters in the name. "Rob G" <RobG(a)discussions.microsoft.com> wrote in message news:D80B76EE-D2D2-47CD-B2B3-4B9F03283013(a)microsoft.com... > Thank you both for your replies. The form is still open and I have tried > to > set up a simple example using one text box from the form as a prototype > for > this problem. > > Private Sub Detail_Format(Cancel As Integer, FormatCount As Integer) > Me.LabelTEST = Forms!MyForm.MyName > Me.LabelTEST = Forms!MyForm!MyName > End Sub > > Both for lines of code yield the dreaded "Run-time error '-2147352567 > (80020009)': The value you entered isn't valid for this field." > > John's question in part C) All the form's business logic and data come > from > the module. The data that the end user adds to the form gets copied and > manipulated in the module causing other values to change and ultimately > some > sections of the form get refreshed. The the user is done putting in the > data, they choose a report as a view of that data. The goal is to have > them > print that report and then I'll write the appropriate data to the database > from within the module and close the form. > > Sometimes a user has to see their work before they accept the data and > want > to commit it to the database. > > I hope I answered your questions and tried to keep the focus on a simple > example to which we can conquer the larger task. > > Thank you. > > > > "Marshall Barton" wrote: > >> Rob G wrote: >> >> >I am sure I am making a newbie mistake, but I think I have a legitamate >> >problem getting data from a form to a report. >> > >> >I have a very complex UNBOUND access form and it has several command >> >buttons >> >that spawn a few different reports. I know that generally reports have >> >to >> >open a form to get data, but in my case, all the work is done by THE >> >FORM and >> >its module. >> > >> >As far as I can tell, the only way to get data from the form/module is >> >to >> >write the data to the database and then open the report bound to the >> >database. >> > >> >Someone please tell me this is too much work and there is an easier way. >> >I >> >have tried to access the form data from the report, but the data in the >> >form >> >seems to be out of scope for the report. >> >> >> It's certainly more in keeping with a database system to put >> the data in a table. But Access is a very versatile set of >> tools and an unbound report is not unheard of. >> >> If the report can live within the design limits of 200" high >> (using a bunch of sections), then you can easily lay it out >> using text boxes with references to the form's controls: >> =Forms!theform.controlname >> If that's the kind of thing you tried, then you'll have to >> post more details before we can figure out what your problem >> is. >> >> Things get trickier as you try to expand on this basic >> approach. >> >> -- >> Marsh >> MVP [MS Access] >> |