object variable or with block variable not set

Hello and good luck!

I am creating a database for our departments aircraft flight activity. It is comprised of about 15 different tables that track everything from personnel, flight hours, flight activities and so on.

My difficulty is this. The different tables are updated by users through a complex form. The main form (frmFlightInfo) captures data relevant to each flight. A subform (sfrmFlightDetails) captures data relating to each individual event during that flight. This form has several nested subforms on it which update their respective tables.

Everything is now functioning correctly on the forms and all the subforms display the correct info. My problem is that when I click on one of the nested subforms (3rd level), open properties and select data and then attempt to open the dialog box to adjust the linking (Main form, Child Form) - I get the error message . . . "object variable or with block variable not set". I can manually change the linking fields, I just can't get the dialog box to open.

I thought this was no big deal at first, but now that I am attemtping to query data and set up reports, I am finding the data is not linking. In looking at the tblFlightInfo and tblLightDetails, I see there is no data in the fields that I used to link. I have "EventID" set as the linking fields in all these 3rd level nested forms, but their value in tblFLightDetails is empty. I also have my relationships setup, however, I don't know how accurately.

Does anyone have an idea why I am getting this error message, and more importantly, why the data is not linking anywhere except on the Form-Subform?

Also, I have several subforms attached to the main form (frmFlightInfo) that I am able to bring up the field linker box on. They all are storing data correctly. The same goes for sfrmFlightDetails. The problem is isolated to the subforms on sfrmFlightDetails.

I don't know if it makes a difference, but these forms are contained on tab-form with frmFlightInfo and its subforms on the first tab. sfrmFlightDetails and the 3rd level subforms are on the second tab.

Thanks, sorry for the short novel!
caughronAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

peterpuscasCommented:
it looks like you have a wrong name for an object as property for another one
try tools/databaseutilities: repair/compact
check the properties for the forms, controls

Peter
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
caughronAuthor Commented:
I've tried that and it still is producing the error?
0
caughronAuthor Commented:
Also, if I open just the 2nd level subform (sfrmFlightDetails) outside of the 1st level form (frmFlightDetails), I am able to open the Form Linker dialoge box with no error for the nested subforms. It is when I open frmFlightDetails (that contains all the levels) is when I get the error.

Thanks for the help.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

LcassineCommented:
I am experiencing exactly the same problem as described here.  Does anyone have a solution for this problem?
0
trcannonCommented:
So Am I!!!  Any help would be GREATLY appreciated
0
trcannonCommented:
I don't know if this will help anyone...but I had the exact same problem with a nested subform where the "plus sign" no longer showed up to drop down to the nested form.   In the design view, I received this same error when tryiing to change the relationship between the child and parent.  That is when I noticed that I had a totally blank record in my database, which shouldn't be allowed because of required fields.  I still don't know how this  record was saved, but when I deleted it the whole problem was fixed.  Weird!  But I thought I should share this.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.