If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Repost frm 1/27, + some more Q's...
In my quest to acheive a more efficient (dare I say normalized?) database, I
am about to create my new database tables, based on what I've presented in previous posts here. I'm going to use similar table & record names as the current set-up, but I plan to add the "tbl" to each table name, and some other abbreviation to each fieldname, so that I don't get confused working between the two different databases. Should I create the new database in the same filepath as the old one? Something tells me I should not....am I correct? After I create the tables, is there an easy way to transfer the data? I don't necessarily want to transfer all of the data immediately, just about 50 or so records until I am assured that my new set-up works. Just to clarify what I mean by "easy," the old-school me first thought I have to literally type in all the records manually, one at a time .... but then I had a second thought; please tell me there's a better way. Also, is there an efficient way to store phone numbers with extensions? I have used a phone number input mask for the phone number field, but what do I do with the extension? Not every record will have a work phone number, let alone an extension, so is it worth even adding fields for that? And if I do add fields for extensions, what do I do for a record that has none? Leave it empty? Enter something so that the field is not blank, like "n/a"? I can justify my learning database design "on-the-job" because #1, I am learning something new to add to my resume, and #2, it should eventually benefit the employers, but I just feel that plain ol' typing is not worth my time (not like it was 25 years ago, lol). In peace, and thank you all again for the ongoing support, Max |
#2
|
|||
|
|||
Max
Just one person's opinions... (see in-line below) "Max" wrote in message ... In my quest to acheive a more efficient (dare I say normalized?) database, I am about to create my new database tables, based on what I've presented in previous posts here. I'm going to use similar table & record names as the current set-up, but I plan to add the "tbl" to each table name, and some other abbreviation to each fieldname, so that I don't get confused working between the two different databases. Should I create the new database in the same filepath as the old one? Something tells me I should not....am I correct? Not if it will have the same exact name, ... but I've used the same filepath for new and old versions of the same app, and simply renamed the old one "out of the way" when I'm ready to rename the new one to the old name. After I create the tables, is there an easy way to transfer the data? I don't necessarily want to transfer all of the data immediately, just about 50 or so records until I am assured that my new set-up works. Just to clarify what I mean by "easy," the old-school me first thought I have to literally type in all the records manually, one at a time .... but then I had a second thought; please tell me there's a better way. If you open the new one and use File | Get External Data | Link ... to connect to the data source of the old one, you can "see" both old and new tables in your new MDB. Use append queries to move copies of some or all of the data from your old tables to the new ones. NOTE: If you haven't already considered it, this would be a good time to "split" your database. Your new MDB would consist of two parts, a back-end, with tables only, and a front-end, with everything else. Use that Link ... feature to connect the front to the back. Also, is there an efficient way to store phone numbers with extensions? I have used a phone number input mask for the phone number field, but what do I do with the extension? Not every record will have a work phone number, let alone an extension, so is it worth even adding fields for that? And if I do add fields for extensions, what do I do for a record that has none? Leave it empty? Enter something so that the field is not blank, like "n/a"? I don't know what your data structure is, so I'm not sure why this is a concern. For an analogy (but a weak one), would you change how you record a person's name if you had one person who didn't have a middle name/initial, only a first and last name? (you are keeping names separated like this, right?) I would add a field for phone extension... I can justify my learning database design "on-the-job" because #1, I am learning something new to add to my resume, and #2, it should eventually benefit the employers, but I just feel that plain ol' typing is not worth my time (not like it was 25 years ago, lol). In peace, and thank you all again for the ongoing support, Max -- Good luck Jeff Boyce Access MVP |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Repost: MS Access "Network or Disk error" message | Damien McBain | General Discussion | 8 | October 10th, 2004 06:58 PM |
Changing -> File, properties, Summary (A Repost) | Hari | General Discussion | 6 | August 2nd, 2004 08:04 PM |
Repost - Using SUMIF and COUNTA | Max | Worksheet Functions | 4 | May 4th, 2004 07:07 AM |
Repost - Using SUMIF and COUNTA | Peter | Worksheet Functions | 0 | May 3rd, 2004 01:36 PM |
Repost - Referencing values of a record entry, elsewhere! | Russ | Worksheet Functions | 1 | January 21st, 2004 11:27 AM |