We have an app that has been plugging away for about 7 years now.
The primary table has less than 10,000 records and it grows now by a little over 2000 records per year. Its record length is 100 fields (1743 bytes) and is truly flat. There are no 1st, 2nd & 3rd of anything that could constitute one-to-many. We are about to take it from Fox26W to VFP6 and place a major portion of the reporting, done for clients, up on the web with Web Connection.

The Question Is: Is there any reason we should break up the primary table into multiple tables given that they would all remain on a one-to-one basis anyway? Thanks for any thoughts.