Yes, I had that too. But that doesn't work well if you have the database on a shared drive accessed by multiple users.
My solution to this now has been to have a physical temporary table and have users log-in to the database. Now I fill in data into the temporary table inlcuding the userid (so...
Hi, and yes that has been my findings as well and as the temporary feature is a new item for ADO (and it seems not part of DAO) I'm stuck.
Thanks for your info
Serge
Thank you Francescina
I had already looked at that, but I can't get the .Name property to show up or work.I defined the recordset with:
Global rst As ADODB.Recordset
then I used me.recordsoure=rst.Name
and got an error message
Hi
I have created a temporary ado recordset (I had to add some empty rows into and existing recordset). The recordset has now the correct number of rows and I can navigate through them just fine.
But so far I have been out-of-luck trying to get a report to use that recordset as its recordsource...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.