Apologies to all who have been trying to help me with this db design challenge. It appears my explanations of what it’s for and what it’s supposed to do is confusing.
I think I should explain again, simplifying as far as I can for clarity.
It’s as if I had a number - let’s say 10 - standard letters (that I’m henceforth referring to as ‘styles’) that I wanted to personalise and to be able to send to any name on a list except:
• It’s in audio format meaning I can not do a ‘mail-merge’ equivalent.
• Each name has to be recorded and manually ‘mixed’ into each style* so where my set’s complete for one name I have 10 different sound files with the same file name, each kept in a folder named according to style.
• The primary purpose of the database is to let me enter a name and a style and it will tell me if there’s a file ready with that combination.
There are some things that complicate this:
• There are many ways of spelling some names (e.g. abi, abby, abbey, abbie). Looked at another way, there are many names that when pronounced, sound the same as each other! Each of these needs to refer to the same filename (which could be available in any or all styles). This means I need to associate all the spellings of one name to the one file name.
• Also, there are some names that are spelled the same but pronounced differently (e.g. jean – which can be a male’s name which sounds very different from the female’s name with which English speakers are more familiar).
There will always be unusual names that come up which will need to be recorded and mixed for one particular style, used then disposed of. However, the aim is to have 1500 odd files with the most popular names pre-prepared for each (and yes, I am aware of the scale of the project and no, there isn’t another way!) so they can automatically be dispatched as required. I’m guessing linking different spellings will increase the number of names – available in every style – to around 4000.
I hope it’s appropriate that I’ve explained this in detail here. I think it’s required because this db design is such an unusual one that when I'm asking specific things regarding tables, queries etc. I can refer to this for the context.
I’m not asking anyone to do this for me. I want to have done it myself but I need to be borrowing your expertise.
Also, this posting is not a request for any specific help about the project though, of course, any comment is welcome.
The thread which is currently addressing the data structure and table relationship issue is:
http://www.access-programmers.co.uk/forums/showthread.php?t=106356
I will edit this to link to threads looking ad different aspects as I go along (providing this approach is acceptable with the forum community).
Cheers
*This is what’s taking most of my time at the moment (there's a good few thousand already recorded since the project was started).
I think I should explain again, simplifying as far as I can for clarity.
It’s as if I had a number - let’s say 10 - standard letters (that I’m henceforth referring to as ‘styles’) that I wanted to personalise and to be able to send to any name on a list except:
• It’s in audio format meaning I can not do a ‘mail-merge’ equivalent.
• Each name has to be recorded and manually ‘mixed’ into each style* so where my set’s complete for one name I have 10 different sound files with the same file name, each kept in a folder named according to style.
• The primary purpose of the database is to let me enter a name and a style and it will tell me if there’s a file ready with that combination.
There are some things that complicate this:
• There are many ways of spelling some names (e.g. abi, abby, abbey, abbie). Looked at another way, there are many names that when pronounced, sound the same as each other! Each of these needs to refer to the same filename (which could be available in any or all styles). This means I need to associate all the spellings of one name to the one file name.
• Also, there are some names that are spelled the same but pronounced differently (e.g. jean – which can be a male’s name which sounds very different from the female’s name with which English speakers are more familiar).
There will always be unusual names that come up which will need to be recorded and mixed for one particular style, used then disposed of. However, the aim is to have 1500 odd files with the most popular names pre-prepared for each (and yes, I am aware of the scale of the project and no, there isn’t another way!) so they can automatically be dispatched as required. I’m guessing linking different spellings will increase the number of names – available in every style – to around 4000.
I hope it’s appropriate that I’ve explained this in detail here. I think it’s required because this db design is such an unusual one that when I'm asking specific things regarding tables, queries etc. I can refer to this for the context.
I’m not asking anyone to do this for me. I want to have done it myself but I need to be borrowing your expertise.
Also, this posting is not a request for any specific help about the project though, of course, any comment is welcome.
The thread which is currently addressing the data structure and table relationship issue is:
http://www.access-programmers.co.uk/forums/showthread.php?t=106356
I will edit this to link to threads looking ad different aspects as I go along (providing this approach is acceptable with the forum community).
Cheers
*This is what’s taking most of my time at the moment (there's a good few thousand already recorded since the project was started).
