I've been doing an Access project recently, but my previous gig was with Java and it prompted me to explore using OOP techniques with Access, so while I was waiting for my client to get rolling, I developed a non-trivial example of OOP with Access. The example creates a UI for an administrator to assign students to classes; a classic many-to-many relationship. I developed the UI 3 ways: using bound controls, using unbound controls, and using OOP. The bound version took about 2 pages of code. The unbound, about 2 1/2 to programmatically populate listboxes, and the OOP version about 10 pages. The OOP version is pretty sophisticated, though, it uses the Model-View-Controller model with a 3-tier architecture. After finishing, it's clear that the bound version was really quick to develop (an hour of work) at the cost of flexibility and control. The OOP version took nearly 2 days and is really flexible, but seems unjustifiable for a small project. Anybody interested in looking at the code and commenting? I'd be interested in other's opinions.