Patty,
I agree with John's approach as it will allow the system to mange cross month activity, if that's possible, where data is entered at 4 pyem on the last day of a month. This approach would also support the inevitable request for "last 6-months of data for trending purposes" with a simple query and Access report.
I can't help but wonder if "Main FE" implies a FE that is linked to the FE's that reside on user's PCs. I don't think that this is the case but thought I'd mention it simply because I thought of it.
In addition to retaining multiple month's data in the BE, I'd also assess risk associated with the data or its loss to see if it's worth warehousing the data on a monthly basis. This, then, begs the question, is the warehousing going to be automated or manual.
If there are already processes and procedures in place to collect, retain, manage, and report the data, then the tool needs to support them although there are almost certainly going to need to be adjustments made to them as the tool is created and tested. This may, then, present you with the joy of embracing some organizational change.
I'm am by no means suggesting that all or any of this wonderfulness actually needs to be done. I'm just suggesting that, in planning, it's not a bad idea to consider these sorts of things to either do them or to reject them.
Thus endth my 02 cents.
Jeff
---
Jeffrey Park Jones
Excel, Access, Word, Office Expert
919-671-9870
5109 Deer Lake Trail
Wake Forest, NC 27587
I agree with John's approach as it will allow the system to mange cross month activity, if that's possible, where data is entered at 4 pyem on the last day of a month. This approach would also support the inevitable request for "last 6-months of data for trending purposes" with a simple query and Access report.
I can't help but wonder if "Main FE" implies a FE that is linked to the FE's that reside on user's PCs. I don't think that this is the case but thought I'd mention it simply because I thought of it.
In addition to retaining multiple month's data in the BE, I'd also assess risk associated with the data or its loss to see if it's worth warehousing the data on a monthly basis. This, then, begs the question, is the warehousing going to be automated or manual.
If there are already processes and procedures in place to collect, retain, manage, and report the data, then the tool needs to support them although there are almost certainly going to need to be adjustments made to them as the tool is created and tested. This may, then, present you with the joy of embracing some organizational change.
I'm am by no means suggesting that all or any of this wonderfulness actually needs to be done. I'm just suggesting that, in planning, it's not a bad idea to consider these sorts of things to either do them or to reject them.
Thus endth my 02 cents.
Jeff
---
Jeffrey Park Jones
Excel, Access, Word, Office Expert
919-671-9870
5109 Deer Lake Trail
Wake Forest, NC 27587
From: "John Viescas JohnV@msn.com [MS_Access_Professionals]" <MS_Access_Professionals@yahoogroups.com>
To: "MS Access Professionals" <MS_Access_Professionals@yahoogroups.com>
Sent: Saturday, August 30, 2014 7:21:07 AM
Subject: Re: [MS_AccessPros] Looking good advice on new project
--
To: "MS Access Professionals" <MS_Access_Professionals@yahoogroups.com>
Sent: Saturday, August 30, 2014 7:21:07 AM
Subject: Re: [MS_AccessPros] Looking good advice on new project
Patty-
That sounds reasonable. With so little new data coming in each month, you probably don't need to move the data each month. You can set up the front end apps for the data entry people to apply filters to show them only the last two months of data - just be sure you have indexes on your date/time fields.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Aug 29, 2014, at 3:18 PM, Patricia Mapes patty.mapes@gmail.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
I have a new project that I have been asked to do. It involves many users (70-100) putting in very little data (10-50) records per month.
My thought was to give each of these remote users, who log directly into the network a front-end to enter their records into, and then the Main FE is where all the processing will occur (converting trip logs to billing).
The BE will reside on the server, of course.
My draft plan includes removing past months and depositing them into a Data Warehouse as they are only accustomed to seeing the current and one past month.
(Presently they have an unsatisfactory Approach solution which is unsupported in their system.)
My question is, it this a viable solution? Would you recommend it?
Thank you for any insight or recommendations that you have.
Patty
--
Patricia Mapes
--
Patricia Mapes
--
---
Jeffrey Park Jones
Excel, Access, Word, Office Expert
Excel and Access, LLC®
http://ExcelAndAccess.Com
919-671-9870
5109 Deer Lake Trail
Wake Forest, NC 27587
jpjones23@centurylink.net
Jeffrey Park Jones
Excel, Access, Word, Office Expert
Excel and Access, LLC®
http://ExcelAndAccess.Com
919-671-9870
5109 Deer Lake Trail
Wake Forest, NC 27587
jpjones23@centurylink.net
__._,_.___
Posted by: jpjones23@centurylink.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar