thx John i'll use the splitter...

*while testing i noticed that if the user selects a student from the
cboStudent, then you HAVE to select a subject from the cboSubject, else you
cannot do anything until you pick a subject. is there a way to remedy this
in the event the user wants to quit after selecting a student?

i tried adding a btnReset to reset cboStudent to null but cannot continue
until a subject is selected...

"John W. Vinson" wrote:

On Wed, 31 Dec 2008 18:37:01 -0800, mike
wrote:

forgot i wanted to ask about deploying the completed program. curious as to
what obstacles i might face if when i load the .mdb on the teacher network.
-do i copy the .mdb to a network drive for user access (no pun intended
-can mutiple users access it simultaneously?

They can... *BUT THEY SHOULDN'T*.

Sharing a .mdb in this way is a recipe for bad performance, bloat, user
contention, and risk of corruption.

Instead, use Tools... Database Utilities... Database Splitter Wizard to
"split" the database into a Frontend (containing the forms, reports, queries,
and code) and a Backend (containing the tables). Each user gets a copy of the
frontend, linked to the shared backend.

For details see http://www.granite.ab.ca/access/splitapp.htm or Google for
"Access split database".
--

John W. Vinson [MVP]