Posted on 2013-01-23
Last Modified: 2013-01-30
Hi All.
I need to dyamically assign source-data fields (in RecordSource) to report (detail) fields (DAO) upon report load. (need to use one report-template for multiple queries of unknown field-names or number of fields.
(I have done the labels but cannot locate the properties the data fields)
Does anyone have a one-line assignment statement / code snippet that assigns source fields to report fields?
e.g. report.fields(2).ControlSource = Me.Recordsource.Fields(F2)

I can do the looping etc. just need the core properties.
Question by:COACHMAN99
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 7
LVL 85
ID: 38812429
Report.Controls("YourControlname").ControlSource = SomeFieldname


Report.Controls(2).controlsource = SomeFieldname

Better yet, build your report based on a query that outputs generic field names:

SELECT fieldA AS Field1, FieldB AS Field2, FieldC AS Field3 FROM MyTable

Now when you need to open the report, just change the SQL of that query:

Dim qdf As DAO.QueryDef
Set qdf = Currentdb.QueryDefs("YourQueryname")
qdf.SQL = "SELECT CustomerName As Field1, CustomerPhone As Field2, '' As Field3 FROM Customertable"
Set qdf = nothing

If your report is based on the query named "YourQueryName", you could then open the report and it would show you data from Customertable.

Author Comment

ID: 38812632
Thanks for attempt.
the missing part is your 'somefieldname' e.g. Me.Recordsource.Fields(F2)
(which doesn't work).
What is the syntax for referencing the datasource field / data?
I've tried recordsource and recordsetcloe but haven't quite got it.

LVL 85
ID: 38812642
"FieldName" is just the name of a field defined in your recordsource. I'm not sure how you'd do this; you might try


However, review the QueryDef method I suggest in my earlier comment.
Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.


Author Comment

ID: 38812695
thats one of the things I tried before posting (see original post above).
I also did a partial imlementation of the querydef before posting.
For my requirement I really need the syntax for addressing fields in the datasource of the report.
LVL 85
ID: 38812760
One of the issues with this is that you're dealing with a Report, which sets the Recordsource and such much earlier than a Form.

hats one of the things I tried before posting (see original post above).
I don't see where you use the RECORDSET ... but I could be mistaken. Regardless, the best method to use to set field names dynamically on a report is to use the QueryDef method described above.

You could also use a temp table. Build a temp table that has fields named like "Field1", "Field2", etc etc, and base your report on that. Now fill the temp table using VBA before opening the report.

Author Comment

ID: 38812996
While I was waiting for input from EE I also implemented a temp table/vba solution although, for my requirement I really need the syntax for referencing fields in the datasource of the report.
I will wait a while to see if anyone has the required object-model/syntax.
thanks for the attempt.
LVL 85
ID: 38813808
Have you tried doing this in the OPEN event of the report instead of the LOAD event? The OPEN event might give you a better handle to the datasource.

Author Comment

ID: 38815025
II tried both, the (data) objects are limited (better in adp).
LVL 85
ID: 38815700
I'm just not sure you can do this (i.e. set the ControlSource of a report's controls at runtime). I could be wrong, but I recall trying this long ago and abandoning it in favor of the query approach suggested earlier.

Author Comment

ID: 38816655
you can. I need to reference the datasource properties/fields.
LVL 85
ID: 38816808
If you can't get it from the report's RecordSource or from the report's Recordset then you're out of luck. There are no other "datasource" properties of the Report object (other than RecordsetClone, which is just a clone of the Recordset).

Author Comment

ID: 38836666
the fact that the (datasource) properties are accessible in the designer implies they are referenceable at runtime. Maybe the parent object isn't ME.?
LVL 85

Accepted Solution

Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 500 total points
ID: 38837102
There are many design-time properties that are not available during runtime (and vice-versa). Some may be accessible, but in a read-only state (for example).

Maybe the parent object isn't ME.?
The ME qualifier just refers to the currently active object, whatever that may be. In  your case, that's the Report object. If you were working with a Form, then ME would refer to the active form ...

This seems to work:

 Dim rs As DAO.Recordset
    Set rs = CurrentDb.OpenRecordset("SELECT * FROM rv_prov_addinfo")
    Me.RecordSource = rs.Name
    Me.txSequence.ControlSource = rs.Fields(0).Name
    Me.txType.ControlSource = rs.Fields(0).Name

Notice the rs.NAME value - that seems to be the critical part. I did this in the Open event of the report.

Author Closing Comment

ID: 38837548
That is my point: If one can assign (and reference) the recordset at runtime, why not at design time? (the object obviously knows which data fields are applied to which report fields).
I have implemented another solution, so will not pursue this any further. Points awarded for effort - thanks.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A simple tool to export all objects of two Access files as text and compare it with Meld, a free diff tool.
Access developers frequently have requirements to interact with Excel (import from or output to) in their applications.  You might be able to accomplish this with the TransferSpreadsheet and OutputTo methods, but in this series of articles I will di…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
In Microsoft Access, learn the trick to repeating sub-report headings at the top of each page. The problem with sub-reports and headings: Add a dummy group to the sub report using the expression =1: Set the “Repeat Section” property of the dummy…

695 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question