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
__._,_.___
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar