Lee Ann

Typically, you'll find the folks here volunteer their time (the Code of
Conduct prohibits solicitation). So if you ask folks to take on extra duty,
outside the 'groups, you may want to seek out paid assistance.

Rather than take that step, could you obfuscate your data (if the data is
what's sensitive)? If it is the design itself that's proprietary, could you
use an analogy? For example, here's a simplistic design for a registration
database:

tblPerson
PersonID
FName
LName
DOB

tblClass
ClassID
ClassTitle

trelRegistration
RegistrationID
PersonID
ClassID
RegistrationDate

One record from tblPerson could have many trelRegistration records.

One record from tblClass could have many trelRegistration records.

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Lee Ann" wrote in message
...
Is it possible to post my tables and relationships for advice and to do so
privately? I posted a couple questions on this DB and based on responses,
I'm beginning to doubt my entire design. Unfortunately, this DB is of a
sensitive nature and posting the entire information to be captured on an
open
forum is not an option.

Thanks in advance.