[AccessDevelopers] File - Monthly_Notices.txt

 

Monthly notices:

Hi Kids!:

Don't forget to check out our "Links" section at the website for helpful sites. Also take a peek at books that others have found worthwhile in our books database under the 'Database' link of the main AccessDevelopers page. Feel free to add any books or links that you have found useful.

__._,_.___

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (171)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Please zip all files prior to uploading to Files section.

Visit Your Group

• Privacy • Unsubscribe • Terms of Use

SPONSORED LINKS

.

__,_._,___

Re: [MS_AccessPros] Database design - best practice

 

Duane

I found the Access Project Management template that comes with Access.  With a bit of redesigning to move everything down a level (the database is for one project, table "Projects" becomes tblRequirements, table Tasks remains but becomes tasks of the requirement and I create another table for details of tasks - linking to Word documents etc) I have a workable solution.  Most of the embedded forms and reports don't need much tweaking.

Thanks for the nudge in the right direction.

Ray

---In MS_Access_Professionals@yahoogroups.com, <duanehookom@...> wrote :

Ray,

When you stated "Access being the preferred route" I assumed you wanted to build your solution in Access.

Duane

---

From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com> on behalf of rayfrew@... [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com>
Sent: Thursday, September 27, 2018 7:04 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Database design - best practice

 

Hi Duane

Thanks for your thoughts.  I hadn't thought of creating a database to manage the project but I like the idea of linking to other, more specialist types of files (Word, Excel, MS Project etc).  I'll experiment - thanks for the prompt.

Best regards

Ray 

---In MS_Access_Professionals@yahoogroups.com, <duanehookom@...> wrote :

I'm not sure Access alone can/should handle all of these requirements. I would suggest as just a kick start for discussion three tables:

 tblProjects

 tblTasks

 tblDetails

Projects is the top level with Tasks being a child of projects and Details being a child of Tasks. Each of these tables would have fields like:

Title

Description

ExpectedDate

CompletionDate

PercentComplete

ResponsiblePerson

Sequence

This could probably managed in a single table with parent and child IDs. At the project level there could be links to project documents and project notes.

You might also want to incorporate Word docs, MS Project or Planner as well as other tools.

Duane

---

From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com> on behalf of rayfrew@... [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com>
Sent: Wednesday, September 26, 2018 4:45 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database design - best practice

 

Hi Everyone.  

I'd appreciate your thoughts and pointers about how to design, track development and achieve customer acceptance of a database (Access being the preferred route).

I would have a workflow of:

1. Discuss what the customer wants - this gets you Quality expectations, Acceptance criteria and major requirements.

2. Break the major requirements into smaller requirements which can be prioritised and estimated.

3. Create a plan for the tasks (design db, design style, build tables, queries, forms, test, and no doubt change)

4. Cope with change (oh, by the way, can you just...)  (I don't like it ....)

What I'm interested in is techniques and/or tools to manage / track the above.  Most of the books I've read about Access go into the techniques of how to use Access but don't mention the User / Business reasons for having a database in the first place.  Any hints, tips, websites, books, forums, ideas welcomed.

Many thanks

Ray

__._,_.___

---

Posted by: rayfrew@gmail.com

---

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (7)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Visit Your Group

• New Members 1

• Privacy • Unsubscribe • Terms of Use

SPONSORED LINKS

.

__,_._,___

RE: [MS_AccessPros] Database design - best practice

 

Hi Bill

Thanks for your thoughts.  I realise that I was looking for a magic piece of software that would help me keep track of the questions and answers, that would mind map the design, that would track the progress of development and testing and have some form of burn chart to show that everything was on time and on budget.  Magic software doesn't exit - all the magic happens in the mind and the mechanics of how to keep track of things is a personal choice, a comfort thing.  I'll experiment with Duane's idea, try OneNote, use Word, Excel and MS Project where they add value, draw lots of diagrams and buy lots of Post-It notes.  The discussions with the clients are the key.

Thanks for your help.

Best regards

Ray

---In MS_Access_Professionals@yahoogroups.com, <wrmosca@...> wrote :

Ray – I always start with these questions: What are you doing now to accomplish your goal? What are you not happy about the current situation?

 

Get exact steps including the time it takes to do those steps. That will give you the current workflow. Workflow charting is your #1 document. Users won't be happy if you mess up what they are already doing unless it saves them tons of effort and time.

 

My very first big database was a financial reporting database that gathered data from several sources that included flat files, databases, spreadsheets. The original database took 40 hours a month to be able to spit out the various reports. Most of the work was cut and paste into tables.

 

When I finished with my application the process took 30 minutes. I felt bad that the thing was so easy to use that the person previously doing the job was let go. But I got a huge paycheck for that contract so the sadness was short-lived.

 

Every database application is basically gathering data and presenting it in a meaningful and easy way. Every database has basically the same elements: tables, queries, forms and reports. It's how you organize the user interfaces that make or break its usefulness and longevity.

 

 

 

Regards,
Bill Mosca,
Founder, MS_Access_Professionals

MS Access MVP 2006-2016
That'll do IT http://thatlldoit.com

My Nothing-to-do-with-Access blog

https://wrmosca.wordpress.com

 

From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Wednesday, September 26, 2018 2:46 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database design - best practice

 

 

Hi Everyone.  

I'd appreciate your thoughts and pointers about how to design, track development and achieve customer acceptance of a database (Access being the preferred route).

I would have a workflow of:

1. Discuss what the customer wants - this gets you Quality expectations, Acceptance criteria and major requirements.

2. Break the major requirements into smaller requirements which can be prioritised and estimated.

3. Create a plan for the tasks (design db, design style, build tables, queries, forms, test, and no doubt change)

4. Cope with change (oh, by the way, can you just...)  (I don't like it ....)

 

What I'm interested in is techniques and/or tools to manage / track the above.  Most of the books I've read about Access go into the techniques of how to use Access but don't mention the User / Business reasons for having a database in the first place.  Any hints, tips, websites, books, forums, ideas welcomed.

 

Many thanks

Ray

__._,_.___

---

Posted by: rayfrew@gmail.com

---

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (6)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Visit Your Group

• New Members 1

• Privacy • Unsubscribe • Terms of Use

SPONSORED LINKS

.

__,_._,___

RE: [MS_AccessPros] Database design - best practice

 

Ray – I always start with these questions: What are you doing now to accomplish your goal? What are you not happy about the current situation?

 

Get exact steps including the time it takes to do those steps. That will give you the current workflow. Workflow charting is your #1 document. Users won't be happy if you mess up what they are already doing unless it saves them tons of effort and time.

 

My very first big database was a financial reporting database that gathered data from several sources that included flat files, databases, spreadsheets. The original database took 40 hours a month to be able to spit out the various reports. Most of the work was cut and paste into tables.

 

When I finished with my application the process took 30 minutes. I felt bad that the thing was so easy to use that the person previously doing the job was let go. But I got a huge paycheck for that contract so the sadness was short-lived.

 

Every database application is basically gathering data and presenting it in a meaningful and easy way. Every database has basically the same elements: tables, queries, forms and reports. It's how you organize the user interfaces that make or break its usefulness and longevity.

 

 

 

Regards,
Bill Mosca,
Founder, MS_Access_Professionals

MS Access MVP 2006-2016
That'll do IT http://thatlldoit.com

My Nothing-to-do-with-Access blog

https://wrmosca.wordpress.com

 

From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Wednesday, September 26, 2018 2:46 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database design - best practice

 

 

Hi Everyone.  

I'd appreciate your thoughts and pointers about how to design, track development and achieve customer acceptance of a database (Access being the preferred route).

I would have a workflow of:

1. Discuss what the customer wants - this gets you Quality expectations, Acceptance criteria and major requirements.

2. Break the major requirements into smaller requirements which can be prioritised and estimated.

3. Create a plan for the tasks (design db, design style, build tables, queries, forms, test, and no doubt change)

4. Cope with change (oh, by the way, can you just...)  (I don't like it ....)

 

What I'm interested in is techniques and/or tools to manage / track the above.  Most of the books I've read about Access go into the techniques of how to use Access but don't mention the User / Business reasons for having a database in the first place.  Any hints, tips, websites, books, forums, ideas welcomed.

 

Many thanks

Ray

__._,_.___

---

Posted by: "Bill Mosca" <wrmosca@comcast.net>

---

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (5)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Visit Your Group

• New Members 1

• Privacy • Unsubscribe • Terms of Use

SPONSORED LINKS

.

__,_._,___

Re: [MS_AccessPros] Database design - best practice

 

Ray,

When you stated "Access being the preferred route" I assumed you wanted to build your solution in Access.

Duane

---

From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com> on behalf of rayfrew@gmail.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com>
Sent: Thursday, September 27, 2018 7:04 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Database design - best practice

 

Hi Duane

Thanks for your thoughts.  I hadn't thought of creating a database to manage the project but I like the idea of linking to other, more specialist types of files (Word, Excel, MS Project etc).  I'll experiment - thanks for the prompt.

Best regards

Ray 

---In MS_Access_Professionals@yahoogroups.com, <duanehookom@...> wrote :

I'm not sure Access alone can/should handle all of these requirements. I would suggest as just a kick start for discussion three tables:

 tblProjects

 tblTasks

 tblDetails

Projects is the top level with Tasks being a child of projects and Details being a child of Tasks. Each of these tables would have fields like:

Title

Description

ExpectedDate

CompletionDate

PercentComplete

ResponsiblePerson

Sequence

This could probably managed in a single table with parent and child IDs. At the project level there could be links to project documents and project notes.

You might also want to incorporate Word docs, MS Project or Planner as well as other tools.

Duane

---

From: MS_Access_Professionals@yahoogroups.com <MS_Access_Professionals@yahoogroups.com> on behalf of rayfrew@... [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com>
Sent: Wednesday, September 26, 2018 4:45 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database design - best practice

 

Hi Everyone.  

I'd appreciate your thoughts and pointers about how to design, track development and achieve customer acceptance of a database (Access being the preferred route).

I would have a workflow of:

1. Discuss what the customer wants - this gets you Quality expectations, Acceptance criteria and major requirements.

2. Break the major requirements into smaller requirements which can be prioritised and estimated.

3. Create a plan for the tasks (design db, design style, build tables, queries, forms, test, and no doubt change)

4. Cope with change (oh, by the way, can you just...)  (I don't like it ....)

What I'm interested in is techniques and/or tools to manage / track the above.  Most of the books I've read about Access go into the techniques of how to use Access but don't mention the User / Business reasons for having a database in the first place.  Any hints, tips, websites, books, forums, ideas welcomed.

Many thanks

Ray

__._,_.___

---

Posted by: Duane Hookom <duanehookom@hotmail.com>

---

Reply via web post

•

Reply to sender

•

Reply to group

•

Start a New Topic

•

Messages in this topic (4)

---

Have you tried the highest rated email app?

With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

---

Visit Your Group

• New Members 1

• Privacy • Unsubscribe • Terms of Use

SPONSORED LINKS

.

__,_._,___