Microsoft Access not able to create subform

no screenshot?

Where are you seeing "Unbound"?

<The first two times it prompted me for a table to use for the subform and it populated the form for me. >
I have never had this happen to me...? I just drop the form in.
...Now, it might ask for the "Linking Fields"

And the linking field screen should only appear if the two tables are not related directly...

Sounds like you disabled the controls wizard accidentally.

- Open your form in design view
- In the Design Tab on the ribbob, click the down arrow on the right hand side of the toolbox where all of the controls are displayed.
- Ensure that the control wizard is enabled.

I think mbizup has your answer, so you can ignore my post above...

I posted the screenshot. That is where it says unbound. I got lucky twice as it did not say this. I don't know how I got lucky. I cannot explain what I did prior to it working twice.
I saw it work in a video and it did work but not anymore.
Is there another way to create subforms that get dropped onto your main form?
When I use the form wizard it creates a form alright but how do I tell it to drop the form onto my main form?
Basically I have a set of command buttons on the left and each one will pull up a subform.
problem.PNG

What I typically do is create my subforms as standalone forms first - I find them easier to work with in their own windows.

Then after saving them, I open my main form in design view and do either of two things...

1.  Click on the subform's name in the navigation pane and drag it to my mainform's design

Or

2.  Get a subform control from the toolbox, place and size it on my mainform's design, and follow the wizard prompts to select a *form*... the previously created subform... (not a table)

ok, I will try to create a form in design mode regular and drag it to my main form like you say above.
I have lost my navigation view and cannot find it again. I have created a form with my fields. Thanks Access! Can I make this into a split form somehow? How do I get navigation view back. What I'm after is how do I drag it to my main form?

Your second method though. That is the problem I think. The wizard does nothing all of a sudden.

Can you upload a sample database?

But first try this...

-- Exit the database
-- Reopen it, holding down the shift key as you are opening it.
-- If the nav pane still is not showing, hit F11.

ok, I have the navigation pane and created the split form I want. Now to somehow drag it to my main form so it sits on my main form. You say drag it but no. No luck with this so far.

No sending a sample db is not possible.

Actually I can drag it to my main form but only a blank box shows up. Where are all the things on the subform?

You're not 'reusing' the same form multiple times as subforms on your mainform are you?  This will have the effect you are describing.

Try doing this *without* a split form first - just a mainform with a single embedded subform.

ok, I have the split form on my main form now. It is not the same design as the ones I was able to put there using the old mysterious method that now won't work. I guess I have to experiment. Seems to be the way to work with Access -try this and that and hope it works each time. Let me play with this for a while. Thanks. I'll try what you said.

Can a split form carry over to the main form? I ask because I only get the top part of the split form on my main form. The bottom half of the split form does not render on the screen. But it did when it was a standalone form. Is it possible Yes or No. If Yes, I'll see how. If you don't mind.

I read your link for Access 2007. It seems fine but I have Access 2010 Professional Plus. My form creation wizard does not offer options like that. I have no sub-form wizard at all.
Can you tell me if it is possible to create a split form in individual form mode and then drag it onto my main form without losing functionality?
The bottom component (the table row view) disappears when I drag it to my main form.
I believe this is all I need to finished with this Access project. ie: a form for each table to allow for adding and modifying records.

I am running Access 2010 Professional Plus as well, and the Access 2007 tutorial definitely still applies.

I can understand your reluctance to post your database, but we really have nothing to go on here.  What you are describing is not "normal" behavior, and without actually seeing your database it is very difficult to determine what the issue is.  It could be a setting within Access... it could be your forms' design... it could be anything.

If you are able to post a sample containing just the forms and empty tables, that would be ideal (we do not need actual data if the data is sensitive).  Screenshots might help too... but so far there is nothing 'visual' here that might help pinpoint the problem.

Regarding split forms, I generally avoid them.  I find the design rigid and prone to problems such as you are describing in your last comment.

Perhaps other Experts here can offer more.

Your advice has helped regardless. I have abandoned the idea of using split forms. I have done my best to use this unbelievable design environment. How would you create a exe from it so the user only sees the form and nothing else? And perhaps even more important how would you allow yourself to continue to have access to the design environment.?
Is it possible to cut an exe from this and leave the design environment intact? I may have to go in and make changes.
I know my question is about subforms but this would really finish this question out.

Regarding making an executable, read this article - specifically about making accde/mde files:
http://msdn.microsoft.com/en-us/library/cc136539(v=office.12).aspx

Generally, you should make an accde or mde to distribute to your users, and have a working/current accdb/mdb for any development work.  

That said, the accde/mdb file is not quite as tight/secure as, say, an executable compiled from a Visual Studio project.  Access inherently is not particularly secure, but it is adequate for many office productivity applications, and for your developer dollars (or whatever currency) it is pretty good.  

If you need rock-solid security in your applications though, Access is not the right environment.  Something like Visual Basic or VB.net with a SQL Server back-end would be more appropriate ($$$).