Help with Design

Hello

I have a customer who has been using Paradox and they have requested that I
transition them from Paradox to Access. I have no idea about Paradox but it
seems to not follow normal database conventions - at least the way my
customer explains some its processes.

My question is as follows...

Currently in Paradox my customer has about 8 tables that contain identical
fields. Each table is for a different client and therefore only contains
data for that particular client. Each table has a predefined name say 8162,
8163,8164,8165 etc. These names are associated directly with billing codes
that are required to be changed on a yearly bases. Since there is no
association of data in the table (no field in the table that contains "8162"
etc.)with the table name, the only way for my customer to know which table
the data came from is to name the extraction file. These tables are not
linked, so when my customer needs to query all activuty for 2006, he must
extract data from each table.

Originally my customer requested that I keep the same design in Access yet
they also wanted to be able to consolidate the data from each table to allow
the creation of reports without having to first extract data from each table.
My customer also requested that if I were to consolidate the tables into one
that I provide the ability to allow data entry without having to remember
which "Billing code" they were entering data for. To accomdoate these
requests, I consolidated all the tables into one table provided filtered
views of each billing codes data. When data entry is necessary, I have a
hidden text box that is bound to the underlying source table and populates
automaticly with the billing number of the view they are in. The new record
then contains the billing number without the individual user having to input
the billing number for each new record.

Secondly:

Since the customer is required to change the billing number each year, I
created a form to allow the customer to change the menu item on the form to a
new billing number which will then update all the old billing numbers to the
new billing number. i.e. 8162 needs to be changed to 8172. My code queries
all records in the table where 8162 is the current billing number and updates
each to 8172.

My delimma,

The customer does not want to lose the old billing numbers! I don't know a
way around this except to create a historical table and add all the
transaction to the table before updateing the billing number. My customer
doesn't seem to be happy with the idea of having 2 tables and having to
remember which one to go to for information. I know, they are currently
using more then 2. I think it's just that they are use to Paradox. Any
ideas? I can't help but wonder if I am going about this the wrong way. I
think that Paradox doesn't change the record billing number only because the
billing number never gets updated at the record level. I say I think becuase
I haven't actually worked on the Paradox database and I am unfortuneatly
dependent upon my clients descriptions. All I know is that it looks like a
DOS screen - big white letters with an awful blue background.

Any help/insights would be appreciated.

Thanks

--
Message posted via http://www.accessmonster.com

.

Relevant Pages

  • Re: Help with Design
    ... It's not Paradox that isn't following the conventions - it is the original ... Congratulations for convincing your customer to allow you a redesign! ... something (NOT the billing code)? ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Help with Design
    ... In the report, the subassemblies can be grouped by sub field, but I ... I have a customer who has been using Paradox and they have requested that I ... These names are associated directly with billing codes ...
    (microsoft.public.access.tablesdbdesign)
  • Re: General question on charging for data access
    ... >>metric for value received by a customer. ... >Connection time no longer provides a good metric, ... Consider a charge per query or a charge per unit of data. ... billing process by ...
    (comp.lang.php)
  • Re: Need help setting up a Parent form with three subforms
    ... you should have additional tables if you are going to include inventory control... ... (customer name, customer address)" ... For instance, a company may have two addresses -- ie, for billing and shipping. ... I am assuming this is your Quotes table ...
    (microsoft.public.access.forms)
  • Re: Need help setting up a Parent form with three subforms
    ... (customer name, customer address)" ... Addresses (with an AddrTypeID specified -- billing, shipping, or both) ... I am assuming this is your Quotes table ... CustEqID and store a long integer CustEqID in the Quote table -- by ...
    (microsoft.public.access.forms)