I am struggling to answer your questions. I don't think I've
succeeded, but I've tried anyway.
My comments are in-line below.
I am not sure what this list represents.
This link leads to a Google internet directory for chats and forums.
I am not sure what this link has to do with your post.
If your filepath exists, it is ok.
Database Design for Mere Mortals by Michael J. Hernandez
SQL Queries for Mere Mortals by Michael J. Hernandez, John L. Viescas
Tips to Get You Going
Microsoft: Description of database normalization basics in Access 2000
(not significantly changed by Access 2007, see the article's own
references at the end to material from the early 1990s).
MS Access Desing:
Building Microsoft Access Applications, by John L. Viescas
Don't repeat what?
For MS Access, backups are best conducted when no users are using the
For concurrent database backups that are accurate and reliable, you'll
need a different database product.
So there is a multi-user requirement?
Split your database.
You would design your database settings and Forms so that data
wouldn't be modified at the wrong time.
I'm not sure what you mean, can you clarify?