Form not saving data...

[centre21]

I've created a form in Access 2003, and when I click "Save Record",
nothing happens. This is a fairly complex form, with tabs/pages and
all manner of controls. I'm not sure if any of that has anything to do
with anything, but I thought I'd mention it anyway.

Also, due to the complexity of the form, I started with the form first
and plan to associate a table with it after I've finished the form
design.

 

[Gina Whipp]

centre21,

Ummm, save what record as you say you have created the form and no table?
So I am unclear what you are trying to save???

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Jerry Whittle]

It's an unbound form then. If you don't have a table, there's no where for
the data to save to. If I read this right, you are building the database
bass-ackwards. You should design the tables first, with a lot of thought
towards normalization, and only then design queries, forms, and reports.

 

[centre21]

It's an unbound form then. If you don't have a table, there's no where for
the data to save to.  If I read this right, you are building the database
bass-ackwards. You should design the tables first, with a lot of thought
towards normalization, and only then design queries, forms, and reports.

Jerry,
You've read it right, there's "unbound" all over the place. Is there a
way to bind it now?

 

[Jerry Whittle]

Not really. You've gone about it the wrong way. You MUST figure out your
tables first based on the data requirements. You might be able to use your
form as a guide to creating the tables, in much the same way as a paper form
might tell you what data is needed. I bet that if you properly normalized
your data and tables, your current form will be useless.

I highly recommend getting some relational database training or reading
"Database Design for Mere Mortals" by Hernandez before proceeding any further
on this database.

 

[John W. Vinson]

Also, due to the complexity of the form, I started with the form first
and plan to associate a table with it after I've finished the form
design.

If you were building a house, would you frame in all the doors and windows,
install the glass, attach the trim...

and then decide where to pour the foundations?

Sorry, but your approach is backward. Tables are FUNDAMENTAL, and are the
basis of your database. You should fit the forms to the (properly
normalized!!) tables, not vice versa!