static Access possible?

[Siozbuag Sepp via AccessMonster.com]

I work for a company that uses Access to create forms and reports based on
data from our service department, and we'd like to help streamline our A/R by
using Access (since we are a tiny company). The problem we are finding is
that all new data for clients and employees overwrites the existing data, and
I would like to know if there is a way to make a static "backup" (so to say)
of certain forms once a month (or week) so there is a simple data trail to
compliment our complex paper trail. The desire is to be able to pullup
backuped data from previous weeks/months/years to compare to current data.
We thought of using Excel, but that was too static and not program friendly...
anyone have any thoughts to make Access more static or the possible use of
another program?

 

[gls858]

I work for a company that uses Access to create forms and reports based on
data from our service department, and we'd like to help streamline our A/R by
using Access (since we are a tiny company). The problem we are finding is
that all new data for clients and employees overwrites the existing data, and
I would like to know if there is a way to make a static "backup" (so to say)
of certain forms once a month (or week) so there is a simple data trail to
compliment our complex paper trail. The desire is to be able to pullup
backuped data from previous weeks/months/years to compare to current data.
We thought of using Excel, but that was too static and not program friendly...
anyone have any thoughts to make Access more static or the possible use of
another program?

I would suggest you take a look at Quickbooks. It does have some
limitations but you say you're a tiny company. Why try and reinvent
the wheel?

gls858

 

[Albert D.Kallal]

The problem we are finding is
that all new data for clients and employees overwrites the existing data

The above problem is not that of ms-access, but who designed the application
with ms-access. It would be silly to design a accounting package that over
writes every new invoice, and even dumber to purchase such a accounting
package. Do note that there are even commercial accounting packages based on
the same database as ms-access (the JET engine). For example, you can open
simply accounting files with ms-access, since that is the file format that
simply accounting users.

So, if you desire some audit trial, or history keeping, the this is SOLELY
the design issue. Take this up with you developers. And, if they don't know
how to do this, then very likely, the time wasted so far should be refunded
to you, or at least given to the poor to help feed them.

So, there is ABSOLUTE no reason for old data to get overwritten.Remember,
ms-access is a development tool, and you can write a pac-man game in
ms-access, or write a full blown accounting package with history, and
auditing built in. The ONLY limits here are the skills of your developers.

So, changing tools here is not the solution, but one of what you developers
are building. I repeat, this is NOT a ms-access problem, but one only of
design.

 

[Rick B]

Hey Albert, I'd like to see that pac-man game