I supported a MS Access DB for years for my previous company but it was mostly modifying and troubleshooting type support. It was a fairly robust DB (at least in my opinion) and I can always figure out the programming part of things (usually with your help). What I'm really not experienced with is the DB design side of things as I've never had to do it. I'm with a new company now and I'm the only one on staff that has any db experience at all. They have me creating a Sales db and I'm a bit out of my league as far as how to set up the tables and such. The problem I'm having right now is the the size of my tables. I'm going to end up having at least four tables (tbl_MFG_Main, tbl_MFG_Order_Revisions, tbl_MFG_Quote_Revisions and I have to create another one tbl_MFG_Orders). These four tables have the same structure as I have to keep the first sales quote in tbl_MFG_Main and then store the Quote revisions and Orders and Order Revisions in the other three. I'm going to have well over 225 fields in each of these tables. Am I correct in my assumption that when I get close the 255, I need to start thinking about splitting up the data? I've never really done any table normalization. Is it too much to ask for someone to take a quick look at my table (s) and suggest how I can split them out? If so, I understand. I can possibly pay someone a bit if that's what it's going to take. I've atttached the database.
If you need more info please let me know.