Anyone have any problems getting fields to stick in a tabbed form? To try to make this short, I had a problem where a field "sticks" to the parent form and not the tab form. Kind of just goes right through. Noticed that as I drag and drop onto the form the properties shows parenting to "null" or "tab4" or "new form" but not always where you expect to see it. Some tab forms seem to be not well defined or lose boundry definition. The "null" appearing when the entire field and name is over the tabbed form. Of course if you let it go there then the tabbed form looks OK but if you flip though the tabs the lower tabs show that field transposed onto them. If you drag the whole tab box around you see it's stuck on the parent form. Any thoughts?

" All selected elements must have the same parent element to be reparented."

Please don't take offense Mark, but I doubt the above makes a bit of sense to anyone in this world outside of you and Erika. 

I'm having the same sort of problem after creating a tabbed page and fields for that page with the Tutorial on my lap following what instructions there are step by step.  As I move the newly created fields from the parent form to the new one I don't get the message parenting to (name of new form) as the manual advises.  I do get a message parenting to canvas-ghosting.  The fields appear to be on the new tabbed page until I click on the new page.  Then they disappear and turn out to truly be on the canvas behind my new tabbed page.   

I have deleted the tabbed page and all the new fields 4 times and started over again with just the first page intact.   So unless you can add something more in detailed step by step instructions than what's in the manual I'm going to throw in the towel.

BTW: Have not been able to reproduce the events that started this thread. Tried to pull fields off various re-designed tab pages and then drop them to ghosting and then bring them back in. Did not "rubber band" any of the fields. Always dragged and dropped one at a time BTW. Have not seen the
parenting to:null  that seemed to cause the most problems.
May have been an alignment problem. I am now more careful w/ aligning fields than when I started.

Quote:


Bobbi,

What do you mean by over the original page?

I have been using tabs extensively in all sizes and shapes all over my form layouts with fairly good results and am very interested in understanding what you have found.

Thanks

Bobbi,

Thanks for the explanation. It sounds like you have figured out what not to do.

I will take care to avoid that situation. 

Thanks

Just a note to add to the discussion. I've been working on a Q&A translated database and have seen some weird things since adding tabs. A few of my translated fields were much wider than the tabbed pages. If I tried to drag them they would vanish when over a tabbed page. The solution was to move them back onto the parent form, resize and then drag back onto the tabbed page. Confusing at first but easy when you know what to do!

Peter

Quote:


In general, elements that contain other elements must be sized large enough that the elements they contain completely fit inside them. Tabs must be large enough to contain their child elements. Radio Button groups must be large enough to contain all their radio buttons. Etc.