Re: DB design, facilitates Double entries of internal transactions

From: postmaster (postmaster_at_yesandright.com)
Date: 03/23/04 

Date: Tue, 23 Mar 2004 16:50:07 +0800

Thanks again, Adrian,

You are the expert I'm looking for. However, our company decided to have an
in-house development rather than invest money on buying product. It's just
the matter at the management level. I don't have much power to convince them
into any alternatives, in fact. I was hired to be an one-man IT staff in
charge of everything in a small company. My role can be all of this: DBA,
System administrator, network administrator.

I can think of Data cleansing from their existing Excel spreadsheets is
another issue that will give me headache.

I'm wondering should I keep posting my conversation to this news-thread.
This is gonna be a long story.

Leonard

"Adrian Jansen" <qqv@noqqwhere.com> ¼¶¼g©ó¶l¥ó·s»D
:405feacf$1@duster.adelaide.on.net...
> I would start by doing some web searches for available products. And yes
it
> costs you ( and the company ) some time/effort to find a good package.
The
> customer I had, had already spent $100,000 on an inventory control
package,
> and it failed miserably, but mostly, I think, because they never fully
> understood what they wanted. I only got called in to 'fix up' an old
Excel
> package I wrote 20 years ago, and decided to convert it all to Access.
Then
> upper management canned it, after spending a further $30,000 with me, and
> having a working system which the operators were happy with.
>
> Beware add-ons !! You need a *very* clear understanding of how to put
> together a total package before even attempting such a system, never mind
> *adding on* accounting. To my mind thats backwards. Accounting has to
be
> right, and fully working before you ever think about inventory, or you
have
> to keep the two systems totally separate. Inventory control is tricky
> enough, bad accounting can totally screw your company.
>
> Personally I would do some searches, find a package which you with your
> experience know will fit what the company wants, then investigate fully
how
> to use it *in detail*. Make sure you can get good support from the
vendor.
> If it still meets your requirements, convince your management to use it,
and
> be prepared to do all the training/handholding necessary. At least that
way
> you dont have to do the design as well as the training.
>
> I think you have a big task just getting them to accept any change,
judging
> by what you say. Certainly they must understand that computers are not
> magic, and will not "make them fly" with no commitment on their part. Good
> luck.
>
> --
> Regards,
>
> Adrian Jansen
> J & K MicroSystems
> Microcomputer solutions for industrial control
>
>