[AccessD] RE: Database for Small Business

Yes I definitely understand.  I forgot that our email system
changed.  I was able to send one unsecure, I hope everyone can
see that one.  I hope I get some help :)



-----Original Message-----
From:
ime_mailer.4-868094-474642-T4LIIXHL at isimevip01.private.massmutual.com
[mailto:ime_mailer.4-868094-474642-T4LIIXHL at isimevip01.private.massmutua
l.com]On Behalf Of accessd at databaseadvisors.com
Sent: Tuesday, August 24, 2004 2:29 PM
To: Christian, Lorraine
Subject: Re: Database for Small Business


 Lorraine, you will probably get a better response if you "DONT" post a
secure message that requires users to log into a 3rd party website.  w/
so many phishing scams out there, I'm sure you can understand this
position.
 
"lchristian" <lchristian at massmutual.com> wrote:
> Message Redirected by Tumbleweed MMS.
> 
> Original Recipients:
> To: "Accessd at Databaseadvisors. Com (E-mail)" 
accessd at databaseadvisors.com
> Cc: 
> 
> Good morning,
> 
> I would like to develop a very simple database for a small business.
> To start off I believe I need a customer table and an invoice table.  
> 
> The customer table will have basic customer information and
> a CustomerID that is an autonumber.
> 
> The invoice table will have billing information and an InvoiceID
> that is an autonumber.
> 
> First question, can you customize autonumbers?  For 
> example I want my first customer to have an ID of 0001
> and my first invoice to have an ID of 2004.
> 
> Second question, each record in the invoice table will be
> for every invoice that is sent out.  I am stuck on how to
> handle late payments.  I would like to charge 1.5% for
> over 30, 60 and 90 days.  
> 
> So for example.  I send out a monthly invoice for customer 0001,
> he/she does not pay on time.  I now need to send out a 
> second invoice not only charging the customer for the current 
> month, but also the payment that is overdue (last month).  And what
> happens if the customer still does not pay and payments become 60 or
> 90 days past due?   I am not quite sure how to design this table in
order to handle
> what I am trying to accomplish.  
> 
> Finally, the actual invoice (report) has separate fields for current,
30 days, 60 days, etc.  In
> addition to that I has a finance charge field.  Originally I was going
to do a simple
> calculation on the report for the finance charge.  But after thinking
about that, do you
> think I should permanently store the finance charge in the invoice
table?  
> 
> If anyone would like to share with me any tips and/or a sample
database I would
> really appreciate it.
> 
> Thanks so much,
> 
> Lorraine  
> 
> ---------------------------------------------------------
> This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the
person(s) to whom it is addressed. Any use, copying, retention or
disclosure by any person other than the intended recipient or the
intended recipient's designees is strictly prohibited. If you are not
the intended recipient or their designee, please notify the sender
immediately by return e-mail and delete all copies. 
> 
> ---------------------------------------------------------
>