implement for small business

[Guest]

I have just built an access program from scratch, and am doing the data
transfer soon. It seems that all the functions will work once I get the data
from outlook in the right places. What problems should I look out for once I
implement the program for my financial advisor business? I have tried to
think of everything that could go wrong, and ways I can build on the program
in the future. I was hoping someone might be able to share a horror story,
or common mistakes that are normally overlooked.

Thanks for your help.

 

[Larry Linson]

I have just built an access program from scratch, and am doing the data
transfer soon. It seems that all the functions will work once I get the
data
from outlook in the right places. What problems should I look out for
once I
implement the program for my financial advisor business? I have tried to
think of everything that could go wrong, and ways I can build on the
program
in the future. I was hoping someone might be able to share a horror
story,
or common mistakes that are normally overlooked.

Create test scenarios and scripts, based on the requirements and design
documents for your database, making sure they cover each requirement. Then
execute those scripts, and revise the database to correct problems that you
find. If you did not document the requirements and design, there is no
better time than now to do so.

As I said in another post earlier today, it is easy to describe this overall
process, but at the nitty-gritty level it can be a lot of work (but worth
it... you can bet there will be some cases that didn't "leap out at you" and
are thus untested, but rest assured that the user(s) of your database will
find them for you (usually at some highly inconvenient moment).

Larry Linson
Microsoft Access MVP

Larry Linson
Microsoft Access MVP