Solved

ACCESS 2010 DYNAMIC FIELDS DAO

Posted on 2013-01-23
14
313 Views
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.
0
Comment
Question by:COACHMAN99
  • 7
  • 7
14 Comments
 
LVL 84
Comment Utility
Report.Controls("YourControlname").ControlSource = SomeFieldname

or

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.
0
 
LVL 7

Author Comment

by:COACHMAN99
Comment Utility
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.

cheers
0
 
LVL 84
Comment Utility
"FieldName" is just the name of a field defined in your recordsource. I'm not sure how you'd do this; you might try

Me.Recordset.Fields(1).Name

However, review the QueryDef method I suggest in my earlier comment.
0
 
LVL 7

Author Comment

by:COACHMAN99
Comment Utility
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.
0
 
LVL 84
Comment Utility
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.
0
 
LVL 7

Author Comment

by:COACHMAN99
Comment Utility
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.
0
 
LVL 84
Comment Utility
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.
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 7

Author Comment

by:COACHMAN99
Comment Utility
II tried both, the (data) objects are limited (better in adp).
0
 
LVL 84
Comment Utility
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.
0
 
LVL 7

Author Comment

by:COACHMAN99
Comment Utility
you can. I need to reference the datasource properties/fields.
0
 
LVL 84
Comment Utility
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).
0
 
LVL 7

Author Comment

by:COACHMAN99
Comment Utility
the fact that the (datasource) properties are accessible in the designer implies they are referenceable at runtime. Maybe the parent object isn't ME.?
0
 
LVL 84

Accepted Solution

by:
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 500 total points
Comment Utility
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.
0
 
LVL 7

Author Closing Comment

by:COACHMAN99
Comment Utility
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.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

The first two articles in this short series — Using a Criteria Form to Filter Records (http://www.experts-exchange.com/A_6069.html) and Building a Custom Filter (http://www.experts-exchange.com/A_6070.html) — discuss in some detail how a form can be…
In Debugging – Part 1, you learned the basics of the debugging process. You learned how to avoid bugs, as well as how to utilize the Immediate window in the debugging process. This article takes things to the next level by showing you how you can us…
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.

763 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

7 Experts available now in Live!

Get 1:1 Help Now