Creating many forms from one table - Newbie

I am curious if there is any conflict in creating multiple forms from one table? I have imported from excel one worksheet with a slew of fields and its corresponding data in the columns. when I imported this to access 2007, I allowed access 2007 to create the key and now each row has its key.
Would there be any problems (opertating wise) in creating multiple forms from one table using distinct fields from the table and not repeating?
David N

EggHeadCafe - Software Developer Portal of Choice
..NET System.IO Read And Write Files Compared To Scripting.FileSystemObject
http://www.eggheadcafe.com/tutorials...ead-and-w.aspx

On Tue, 06 Oct 2009 17:53:45 -0700, David Negrete wrote:

I am curious if there is any conflict in creating multiple forms from one table? I have imported from excel one worksheet with a slew of fields and its corresponding data in the columns. when I imported this to access 2007, I allowed access 2007 to create the key and now each row has its key.
Would there be any problems (opertating wise) in creating multiple forms from one table using distinct fields from the table and not repeating?
David N

A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

I guess then I would have to create several table for this action. But now that I have one table and many forms, with data in this now, what would be the easier way to go with various tables and relate it to the forms I now have???



John W. Vinson wrote:

Creating many forms from one table - Newbie
06-Oct-09

A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

Previous Posts In This Thread:

On Tuesday, October 06, 2009 8:53 PM
David Negrete wrote:

Creating many forms from one table - Newbie
I am curious if there is any conflict in creating multiple forms from one table? I have imported from excel one worksheet with a slew of fields and its corresponding data in the columns. when I imported this to access 2007, I allowed access 2007 to create the key and now each row has its key.
Would there be any problems (opertating wise) in creating multiple forms from one table using distinct fields from the table and not repeating?
David N

EggHeadCafe - Software Developer Portal of Choice
..NET System.IO Read And Write Files Compared To Scripting.FileSystemObject
http://www.eggheadcafe.com/tutorials...ead-and-w.aspx

On Tuesday, October 06, 2009 9:39 PM
John W. Vinson wrote:

Creating many forms from one table - Newbie
A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

EggHeadCafe - Software Developer Portal of Choice
It's the Process, Stupid!
http://www.eggheadcafe.com/tutorials...ss-stupid.aspx

On Tue, 27 Oct 2009 15:28:57 -0700, David Negrete wrote:

I guess then I would have to create several table for this action. But now that I have one table and many forms, with data in this now, what would be the easier way to go with various tables and relate it to the forms I now have???

Since you have not posted any description of the structure of your table or
the nature of the forms, all I can say is "I don't know".

I'd be very strongly inclined though to restructure your table into a properly
normalized set of tables, and run whatever Append queries you need to migrate
the data into the normalized tables. You may need to rebuild or heavily modify
the forms if they're currently based on a wide-flat table, but... since I
don't know anything about your wide flat table... I don't know how big a job
that would be.
--

John W. Vinson [MVP]

What I have is in the colum -fields- is the information we take from the client, demographics and their information related to our business. As each new client comes in to use our services, a new entry is created,-the rows. I had though of creating several tables, but as the need to acquire information grew so did the fields. I had imported an excel sheet with about 50 entries, but now the things has over 300 entries. in order to created addidtional related tables, would there be a easier safer way then to do it all from scratch and pick and choose what goes on to what table?



John W. Vinson wrote:

Creating many forms from one table - Newbie
06-Oct-09

A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

Previous Posts In This Thread:

On Tuesday, October 06, 2009 8:53 PM
David Negrete wrote:

Creating many forms from one table - Newbie
I am curious if there is any conflict in creating multiple forms from one table? I have imported from excel one worksheet with a slew of fields and its corresponding data in the columns. when I imported this to access 2007, I allowed access 2007 to create the key and now each row has its key.
Would there be any problems (opertating wise) in creating multiple forms from one table using distinct fields from the table and not repeating?
David N

EggHeadCafe - Software Developer Portal of Choice
..NET System.IO Read And Write Files Compared To Scripting.FileSystemObject
http://www.eggheadcafe.com/tutorials...ead-and-w.aspx

On Tuesday, October 06, 2009 9:39 PM
John W. Vinson wrote:

Creating many forms from one table - Newbie
A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

On Tuesday, October 27, 2009 6:28 PM
David Negrete wrote:

Creating many forms from one table
I guess then I would have to create several table for this action. But now that I have one table and many forms, with data in this now, what would be the easier way to go with various tables and relate it to the forms I now have???

EggHeadCafe - Software Developer Portal of Choice
A Brief Review of Generic Collection Classes
http://www.eggheadcafe.com/tutorials...f-generic.aspx

What I have is in the colum -fields- is the information we take from the client, demographics and their information related to our business. As each new client comes in to use our services, a new entry is created,-the rows. I had though of creating several tables, but as the need to acquire information grew so did the fields. I had imported an excel sheet with about 50 entries, but now the things has over 300 entries. in order to created addidtional related tables, would there be a easier safer way then to do it all from scratch and pick and choose what goes on to what table?



John W. Vinson wrote:

Creating many forms from one table - Newbie
06-Oct-09

A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

Previous Posts In This Thread:

On Tuesday, October 06, 2009 8:53 PM
David Negrete wrote:

Creating many forms from one table - Newbie
I am curious if there is any conflict in creating multiple forms from one table? I have imported from excel one worksheet with a slew of fields and its corresponding data in the columns. when I imported this to access 2007, I allowed access 2007 to create the key and now each row has its key.
Would there be any problems (opertating wise) in creating multiple forms from one table using distinct fields from the table and not repeating?
David N

EggHeadCafe - Software Developer Portal of Choice
..NET System.IO Read And Write Files Compared To Scripting.FileSystemObject
http://www.eggheadcafe.com/tutorials...ead-and-w.aspx

On Tuesday, October 06, 2009 9:39 PM
John W. Vinson wrote:

Creating many forms from one table - Newbie
A good spreadsheet design is often a very bad table design (and vice versa).
Access is emphatically NOT "Excel on steroids"!

A Table with thirty fields is an extremely wide table, and a table with a
hundred fields is TOO wide (for anything but a deliberately denormalized data
archive).

You would do MUCH better to construct a set of two, three or more properly
normalized and related tables, and use Append queries to migrate the data from
this unwieldy monster into them. If you have "columns" - fields - with names
like January, February, March; or Sale1, Sale2, Sale3... these need to be
moved from fields in this table into rows in a related table.

That said... you can create a Form with a Tab Control, and put one batch of
textboxes or other controls on each of several pages of the tab control. This
will keep all the data for one record together more easily than several
unrelated forms will.
--

John W. Vinson [MVP]

On Tuesday, October 27, 2009 6:28 PM
David Negrete wrote:

Creating many forms from one table
I guess then I would have to create several table for this action. But now that I have one table and many forms, with data in this now, what would be the easier way to go with various tables and relate it to the forms I now have???

On Tuesday, November 03, 2009 2:53 PM
David Negrete wrote:

Creating many forms from one table - Newbie - John W. Vinson
What I have is in the colum -fields- is the information we take from the client, demographics and their information related to our business. As each new client comes in to use our services, a new entry is created,-the rows. I had though of creating several tables, but as the need to acquire information grew so did the fields. I had imported an excel sheet with about 50 entries, but now the things has over 300 entries. in order to created addidtional related tables, would there be a easier safer way then to do it all from scratch and pick and choose what goes on to what table?

EggHeadCafe - Software Developer Portal of Choice
SQL Server / .NET Database Driven Permissions
http://www.eggheadcafe.com/tutorials...t-databas.aspx