Van,
Thanks again for your response.
My main form is not blank. Neither is my first tier of subforms. It is the
subforms nested within subforms that are blank (and that is only in one
subform - the last one I created). Some are combo boxes that derive their
entry options from another table.
AllowAdditions Property is "Yes." If I am understanding correctly your
meaning of RecordCount, no records have been entered in the new subforms so
there should be none.
The Form structure consists of a Master form with numerous Subforms, most in
the form of combo boxes. Some of the subforms have forms nested within
them. All primary fields are linked (LinkMaster/LinkChild) by the ClientID
(an assigned number). There are no autonumbered fields (except in secondary
tables that contain lists of items accessed by multiple forms). The purpose
of this database is to track a client's medical information (i.e.,
BrandDrug, GenericDrug, Doctor, Pharmacy, MedicalConditions, etc.). All of
these items (e.g., over 1,000 drugs) are listed in separate tables. This
facilitates being able to update information every 6 months using separate
forms without having to replicate the record source for the corresponding
table (the form's record source). A typical record source string would be
as such: the BrandDrug form has as its record source the ClientBrandDrug
table which has as its record source (the complete list of drugs) the
BrandDrug table. The BrandDrug table is the record source for all the
ClientBrandDrug tables (e.g., 6 MonthClientBrandDrug, 12
MonthClientBrandDrug, 18 MonthClientBrandDrug, etc., etc.) which are in turn
the record source for all corresponding ClientBrandDrug subforms (e.g., 6
MonthClientBrandDrug, 12 MonthClientBrandDrug, and so on).
Since the company using this database wants to archive virtually everything
about each client every six months (keeping that data separate from the
previous 6 months), I replicate (in structure only) 15 tables and 15 forms
for each 6 month review. At the time of each review, the client's data is
updated on the primary form with archival data being entered in the review
form. This allows all the Queries and Reports (which are intended to return
a current profile) to function correctly without updating. My review period
forms (6 Month, 12 Month, 18 Month, etc.), which are designed just like the
primary form, are nested together on a single form and separated by page
tabs. It is the 36 Month Review form that will not display its nested
subforms (the review form itself is visible).
Please bear in mind that this set up has worked flawlessly for two years,
and I am only having a problem with the most recent review period (36
months). All prior review periods are functioning correctly, and I have
created the current review period the same way I created all the others.
Therein lies the mystery. This causes me to wonder about the growing depth
and breadth of this database (currently around 150 each, tables and forms,
as well as 50 to 60 each Queries and Reports) possibly exceeding the
capabilities of Access.
It may also be useful to note that, whereas the structure of this database
may seem complex (because of the number of times individual tables and forms
are replicated), it really is not. Sort of like the cockpit of a B-52 where
you have a lot of guages and dials because the aircraft has 8 engines. You
only need to learn how one set works, and all the rest are the same.
Hope this helps you visualize my situation a little better. Personally, I
am really beginning to question the limits of Access, because I am supposed
to go up to 48 months (3 more review periods than I currently have) and I
feel I need to address future problems now, while the database is still
functioning properly. It is possible that we need to find a better, less
convoluted way to archive data. Are there any known limits to the size and
complexity of an Access database? My current mdb file is around 17MB (after
compact and repair).
Thanks for hangin in there with me, Van . . . Fred