BartonTony
New member
- Local time
- Today, 23:06
- Joined
- Jan 26, 2011
- Messages
- 5
Hi All
I am new at database design, etc., so please go easy on me.
I have attached a blank relational database I have designed. The purpose of the d/base is to store Contact (Contact being the primary Table), details but also details of Files I create and incoming letters. I believe I have fully normalised the database, which currently gives 8 Tables: Contact, Address, Email, Phone, Letter and File. Because I had many-many relationships between Contact and Address and also File and Letter, I have inserted link-tables. I then I guess the first things to establish are:
§ Are the relationships setup correctly?
§ The Primary Key to each Table is auto generated but I then have problems with this in the related Table, so I gave it the data-type: Number. However, as a further help, I want to change the format of that generated number by prefixing with for instance, CO for the Contact Table. The format works fine but as a Foreign Key is not accepted. Any help here would be great.
§ I am then going to design Forms and appropriate Macros to automate the system, though I am no expert at Macros, Queries, Reports, etc.
§ The noddy system I currently use (which works – even if incorrect), is, to enter a Contact. If I have their Address, Phone or Email then that is also entered but most times this needs to be completed later or with certain Tables, not at all.
§ The Letter Table will generate an ID which I then physically assign to an incoming Letter or Document and File away.
§ The File Table stores the location (Directory, etc.) of a given File.
§ Will I need to also create Forms for the Link Tables, since I don’t really use them currently?
Another issue is a 'search field'. One of the sub-tables is called: Letter_Search, and all this is is a field to all searches of who a Letter might be from or who a File might be to, etc. Can't think of how this could be implemented, but I have taken entries from existing d/base and placed into mentioned table. Help!!!
Any advice or information will be very welcomed.
I am new at database design, etc., so please go easy on me.
I have attached a blank relational database I have designed. The purpose of the d/base is to store Contact (Contact being the primary Table), details but also details of Files I create and incoming letters. I believe I have fully normalised the database, which currently gives 8 Tables: Contact, Address, Email, Phone, Letter and File. Because I had many-many relationships between Contact and Address and also File and Letter, I have inserted link-tables. I then I guess the first things to establish are:
§ Are the relationships setup correctly?
§ The Primary Key to each Table is auto generated but I then have problems with this in the related Table, so I gave it the data-type: Number. However, as a further help, I want to change the format of that generated number by prefixing with for instance, CO for the Contact Table. The format works fine but as a Foreign Key is not accepted. Any help here would be great.
§ I am then going to design Forms and appropriate Macros to automate the system, though I am no expert at Macros, Queries, Reports, etc.
§ The noddy system I currently use (which works – even if incorrect), is, to enter a Contact. If I have their Address, Phone or Email then that is also entered but most times this needs to be completed later or with certain Tables, not at all.
§ The Letter Table will generate an ID which I then physically assign to an incoming Letter or Document and File away.
§ The File Table stores the location (Directory, etc.) of a given File.
§ Will I need to also create Forms for the Link Tables, since I don’t really use them currently?
Another issue is a 'search field'. One of the sub-tables is called: Letter_Search, and all this is is a field to all searches of who a Letter might be from or who a File might be to, etc. Can't think of how this could be implemented, but I have taken entries from existing d/base and placed into mentioned table. Help!!!
Any advice or information will be very welcomed.
Last edited:
