- Local time
- Today, 18:59
- Joined
- Feb 19, 2002
- Messages
- 43,396
Sounds like you shouldn't be using Access at allAs if I needed another reason not to use reports.
Sounds like you shouldn't be using Access at allAs if I needed another reason not to use reports.
@amorosik I gave you a solution back in #27 which you totally ignored.
So your recordset contains only a single record?
Or is there a loop that you haven't shown in the code that adds multiple records?
The above could be replaced with:
Code:Me.RecordSource = "SELECT TOP 1 " & _ "'" & count & "' AS read_number, " & _ "'" & tdf.name & "' AS table_name " & _ "FROM MSysObjects;"
Then you can either assign the same SQL to your report's RecordSource, or do something like (within your report's Open event):
Code:Me.RecordSource = Forms("YourFormName").RecordSource
However, it seems strange to use a continuous form for just a single record.
The question was answered: it's not possible.The question is not 'what the recordset contains', but whether it is possibile to pass it to the report for feeding and printing
The question was answered: it's not possible.
So now the question becomes: do you want to get the data in to a report and, if so, what's the most effective way of doing so?
... or perhaps there's a better way to gather the data than using an ADODB recordset in the first place?
You have been told multiple times that your solution is not possible. You can keep arguing or you can consider an alternative.But that's not the solution to the question asked
You have been told multiple times that your solution is not possible. You can keep arguing or you can consider an alternative.
If you are dealing with ONE record at a time, use the tempVars suggestion. If you are dealing with multiple records, make a temp table.
we are 49 posts into what is essentially a simple thread.
-Why doesn't this code work
-Recordsets are not supported
-various alternatives depending on how many records you are receiving at one time.
- so may be 10 posts because there are several solutions you can consider.
At some point, the experts will simply stop trying to help.
Then please close the thread.
I've said it in the past and I will say it again. You have issues, and they're not related to Access.Sounds like you shouldn't be using Access at all
Can you also restore the missing posts, as not getting the full picture here?