Add Existing Fields

[steveo0707]

Hello,



When I try adding from the 'Add Existing Fields' section of my input form, I am getting these weird boxes. It's the only form in the database that this is happening on.

[steveo0707]

Hello,

When I try adding from the 'Add Existing Fields' section of my input form, I am getting these weird boxes. It's the only form in the database that this is happening on.



It is just adding a text box, not the Field box and label.

[Micron]

I've never used that approach. Always have added a textbox from the toolbox then bound to the field I need, assuming it has to be bound. Either do it that way or you can manually add a label in the same manner, but then it won't be linked/associated with the control. To be more accurate, a textbox is a control, not a field, although when referred to that way by many, it is understood to be a bound control. At least that's how I view it.

[June7]

Does this happen with every new form with any table?

[davegri]

It is just adding a text box, not the Field box and label.

Notice that your click (or drag) is adding fields to the form's width of almost 16 inches.
Try adding farther to the left, maybe 1 inch or so.

[steveo0707]

Hello June7,

No this only happening with one form in my current database, I'm not sure why it started doing that. I just tried adding a sample form and everything worked fine.

[steveo0707]

Hello Micron,

I am not purposely doing this. This is what I am getting when I try to 'Add Existing Fields'

[steveo0707]

Hello,

Here is the db.

[June7]

You did not post the db file, only the shortcut.

Possibly this is corruption that cannot be explained nor fixed.

Try building form again from scratch.

[steveo0707]

Hello June7,

Here is the db.

[davegri]

You may have posted the wrong DB. None of the forms display as your image shown in post #1 (and you didn't specify which form had the problem).
Also, your tables are designed in a spreadsheet schema, making your existing forms too wide to view without scrolling across. Proper database design does not have repeating data values that display in your forms horizontally.

[June7]

Form NCMR Input Form exhibits this behavior.

What I did: new form, copy all controls from old Input form, set RecordSource, add new fields from field list - they are correct size with labels.

As I said, corruption.

Strongly advise you remove all spaces and punctuation from naming convention.

I agree, db is not normalized and may cause you big headaches down the road. Current schema may or may not be optimal for your needs. If you need to do a lot of statistical calcs, could be a nightmare. It is a balancing act between normalization and ease of data entry/output. "Normalize until it hurts, denormalize until works."

[steveo0707]

Hello,

Thank you everyone for the help. I will create a new form. I created this form this way, because I could not figure out how to x-fer the data to a PDF, nor could I figure out to get the report to save and print current record only.

[Welshgasman]

Hello,

Thank you everyone for the help. I will create a new form. I created this form this way, because I could not figure out how to x-fer the data to a PDF, nor could I figure out to get the report to save and print current record only.

Well if you Google a little, all that will become obvious.

[June7]

I created this form this way, because I could not figure out how to x-fer the data to a PDF, nor could I figure out to get the report to save and print current record only.

That statement makes no sense. Exactly how would you use this form to print only current record?

Reports are for printing. Build report and apply filter when opening.

Printing has no bearing on our comments about normalization.