On Wed, 5 May 2010 15:41:01 -0700, TechieMom
wrote:

Yes, it's a subform. Basically, the whole thing a very lengthy evaluation
form for a project that we broke into pages to make it easier for the
evaluators to fill in. Each project being reviewed is a row entry in the
table. Each page contains a subform with input boxes for part of the
evaluation data; the reviewers open a main form and flip thru the pages via
tabs across the top to enter data for each section. So all 10 pages/subforms
are updating the same table (in fact, the same record) until the reviewer
goes to the next record and repeats the process.

Ummm... I'd suggest a different approach. For one thing, if the record has so
many fields that this is necessary, your table design may require
reevaluation! A 30-field table is getting pretty wide already!

Secondly, it's perfectly possible to have a Tab Control with multiple pages,
with a modest number of controls on each page, all bound to the same record on
the same table.

I know the recordsource DOES contain records - I have verified this visually
(looking at the table data itself) and the other pages/subforms pointing to
the same recordsource show the data just fine.

As for the Allow Updates or Allow Additions properties, I can check those,
but as I said before I compared the working subforms/pages to the one that is
not working and they all appear to be set up identically.

Since nothing changed from the previous years' database to this one except
for the version of Access we're reading it on, I'm afraid it may be some
random glitch related to the MS Office version changes ...

Wouldn't be the first time, alas! You might want to delete this subform;
compact and repair the database; and recreate the subform (and its query) from
scratch, just in case it has some embedded problem.
--

John W. Vinson [MVP]