Hi Richard-
I figured it out - it was the dao library reference that I had to select.  

I do have another question.  After you make it an accde file and push it out to users, you keep the 'unlocked' version for updating and making changes to?  Then when you are ready to publish again you lock that new version and push it out and so on?

I am also wondering your opinion on having 20ish people access one front end file on the network or e-mail out a copy to each of them to put in their individual drive to use?  Are there any pros/cons that I should consider?  My main concern is record locking and having someone sit in the database all day.  I tried coding in and idle timer but I couldn't get that to work so I am leaning toward each of them their own copy.

Thank you.

Lisa

---

Reply from Richard Rost:

Glad you figured it out.

YES! Keep your ACCDB file. If you don't, then you won't be able to make changes and send out an update. You CANNOT make changes to an ACCDE (encrypted) file.

As long as you program the front end to LINK to tables on a back end that everyone has access to (like //SERVER/DataFolder/BackEnd.ACCDB) then you can just email everyone updates and tell them to drop the front end file on the desktops, replacing the old one. I've done that before and it works just fine.