why don't work dao recordsets in access 2010

i put this in my recordset :

Dim db As Database
Dim rs As Recordset

Set db = CurrentDb
Set rs = db.OpenRecordset

and when i make compile i get this error that point on the "set db":
Compile error:
Invalid outside procedure

and i attach a frame picture from the references

reference.jpg
bill201Asked:
Who is Participating?
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Compile error:
Invalid outside procedure
>>

 Your references are fine.  What you've done though is placed the statement outside of a Function or Sub Procedure.

  You cannot simply place it at the top of a module.  It must occur inside a procedure. i.e.

Public Function MyTest()

  Dim db as Database
  Set db = CurrentDB()

End function

or


Public Sub MyTest()

  Dim db as Database
  Set db = CurrentDB()

End Sub

  You've got the statement in the wrong place and it needs to be moved.

JimD.
0
 
pdd1lanCommented:
Dim db As Database
Dim rs As DAO.Recordset

Set db = CurrentDb
Set rs = db.OpenRecordset("select somefiled from table")
0
 
bill201Author Commented:
i make like you said but i still get the error message on the "set" word
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
pdd1lanCommented:
can you add "Microsoft DAO 3.6 Object Library" in your refrences?
0
 
bill201Author Commented:
i tried it and i get this message:
name conflicts with existing module,project or object library
0
 
pdd1lanCommented:
do you use access 2010 64 bit or 32 bits?

0
 
pdd1lanCommented:
do you have AccDB object library in your reference? if yes, uncheck DAO 3.6 and check accDB object library instead?
0
 
pdd1lanCommented:
if you add AccDB object libary in your refrence, you can try your original code instead.
0
 
bill201Author Commented:
i have access 32 bit
and i don't see the accdb in my reference where can i found it?
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
You don't use DAO 3.6 in Access 2007 or 2010. 2007 and 2010 use the new ACE engine, which requires the references you currently have set.

As pddilan suggests earlier, OpenRecordset require a valid SQL Statement or table/query name:

Set rs = db.OpenReocordset("SELECT * FROM SomeTable")

or

Set rs = db.OpenRecordset("qryGetUserNames")

However, it seems you're having trouble on the "Set db = CurrentDB". Is that correct?

You really don't need to use a variable for this. You can do this:

Set rs = Currentdb.OpenRecordset('Your SQL Statement")

If that doesn't work (and you are 100% certain that your SQL statement is valid) then you may have some issues with the installation of Access, or with one of the supporting libraries/files. You may need to do a repair or reinstall of Access or Office.
0
 
bill201Author Commented:
i don't think that you right and this is the problem because still yesterday i was make all the time recordsets like this and nothing happen and yesterday  without any specific reason (i don't install or update Microsoft office or any other software at all)  it's start to make problems  
0
 
pdd1lanCommented:
sorry, typo, I meant "acedao.dll"

C:\Program Files\Common Files\Microsoft Shared\Office14\acedao.dll
0
 
bill201Author Commented:
any way i try this code Set rs = Currentdb.OpenRecordset ("numberst")
and it's not work so i will reinstall access 2010
0
 
pdd1lanCommented:
so you said you don't have problem yesterday.  maybe you need to repair and compact your databse. j
0
 
bill201Author Commented:
it's not just in one database it's in  every database that i open even  new one  (except of vba windows where i put before yesterday a recordset there is working and i  can even add more stuff to the code)
0
 
bill201Author Commented:
i add this file C:\Program Files\Common Files\Microsoft Shared\Office14\acedao.dll

and it's seems that this file was there before and anyway it's  not working
0
 
bill201Author Commented:
i uninstall office and reinstall it again but the problem remains
0
 
bill201Author Commented:
you are so right it's embarrassing that i don't notice this
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<you are so right it's embarrassing that i don't notice this >>

  I tell you it's amazing sometimes what you filter out when reading an error.  I've been caught like that sooo many times myself over the years it is not even funny.

Have a great day,
JimD.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.