Unable to create records from form fields

  • Thread starter Erik S. via AccessMonster.com
  • Start date
E

Erik S. via AccessMonster.com

I am new to access although proficient in excel. I created a form with
simple relationships using access 2003. I did not create a table however.
I was under the impression you could create the form first, and have the
fields from the form, be used as a table. I've tried creating a table with
fields which I assign to the control source in the form view. I've tried
assigning the recordsource.

Is there a way I can just use the Form I created to create the data table
to be used? Please help. I spent a lot of time creating the form, and it
looks nice. Now all I need to do, is figure out how to be able to enter
data into the fields and save them as records.
 
E

Erik S. via AccessMonster.com

Nevermind, I think I got it.

However, is there anyway to be able to write more than 255 characters in a
text box. I need to be able to write a lengthy narrative in one of my form
fields. Is this possible?
 
R

Rob Parker

A textbox control on a form does not have a character limit per se. You can
exceed the 255 character limit for a bound textbox if the field in the
underlying table is of Memo type.

Rob
 
J

John Vinson

Is there a way I can just use the Form I created to create the data table
to be used? Please help. I spent a lot of time creating the form, and it
looks nice. Now all I need to do, is figure out how to be able to enter
data into the fields and save them as records.

Well... no. That's backwards.

A Form is just a movable window which allows you to enter and edit
data stored in a Table. Data is stored in Tables, and only in Tables.

Typically one would build tables first; each Table should have a
Primary Key (a field or combination of fields which uniquely identify
the record). You'll typically have multiple tables, and will need to
define their relationships. Only then would you start thinking about
the form. Designing a table to fit a form (rather than vice versa) is
very likely to lead to an improper, non-normalized table design, so be
careful!

John W. Vinson[MVP]
 
Top