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
  • 7
  • 7
LVL 84
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 84
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.

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 84
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 84
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.
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.


Author Comment

ID: 38815025
II tried both, the (data) objects are limited (better in adp).
LVL 84
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 84
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 84

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

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
HasData 9 36
SQL profiler equivalent in MS-Access 3 42
Importing and Dropping Table in Access 11 24
Set focus on next field when character count = 5 9 12
Introduction When developing Access applications, often we need to know whether an object exists.  This article presents a quick and reliable routine to determine if an object exists without that object being opened. If you wanted to inspect/ite…
QuickBooks® has a great invoice interface that we were happy with for a while but that changed in 2001 through no fault of Intuit®. Our industry's unit names are dictated by RUS: the Rural Utilities Services division of USDA. Contracts contain un…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

912 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

Need Help in Real-Time?

Connect with top rated Experts

26 Experts available now in Live!

Get 1:1 Help Now