Re: renaming tables for each customer, used in one report

Tech-Archive recommends: Fix windows errors by optimizing your registry

Everything is fully normalized.

Each customer is sending me a spread*** of their data (which is just a
list of product codes they are using) for a one time (usually)report that I
prepare and return to them. I guess I could keep appending this info to an
ever lengthening "customer code table" and then have a parameter to limit to
the customer I am generating a report for. I still have to do an import and
now an append vs renaming the table. Also I really have no need to keep
their old code list for more than a week or so. And periodically I'd have to
cull all the old data out eventually. So my old method vs. this single table
method seems to weigh in about equally. But I'll consider trying the latter.
I think it will just be an empirical determination which is the easiest and
least aggravating.

--
Alan


"Jeff Boyce" wrote:

Alan

Having a table named for each Customer is precisely how you'd have to handle
your situation ... if you were limited to using a spread***!
Copying/importing your "flat" Excel data "as is" directly into the
relational model provided by Access pretty much guarantees that you'll "pain
yourself into a corner".

You won't get the easy use of Access' relationally-oriented
features/functions if you insist on feeding it '*** data.

Before you go any further, I urge you to turn off your computer and sit down
with paper and pencil to map out the data structures and relationships.

If "normalization" and "relational" are not terms you're familiar with,
spend time learning about them before resuming your use of Access.

Regards

Jeff Boyce
Microsoft Office/Access MVP


"adgorn" <adgorn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0E32DED0-AC46-4EA3-8517-A5042B254D20@xxxxxxxxxxxxxxxx
I have a report that relies on a query of a table of customer specific data
(imported fr Excel) joined with a couple of other tables whose content is
fixed. I will be generating this report for several different customers
each
day and so will have to import several different sets of excel files
daily.
WHen I built the db, I called the customer table "table1" and so all the
code
references are to that. So today I got 3 new spreadhseets of customer
data
ready for importing to Access. I am bringing these in as "table1CustA",
"table1CustB" and "table1custC". The original table1 I have contains
bogus
data that I used just for db design purposes. So my plan was to simply
delete table1, then rename table1CustA to table1 and run the report for
CustA. When this is done I would rename table1 back to table1CustA, then
rename table1CustB to table1 and run CustB's report, etc. Can I just do
this
w/o worrying about the order of how I rename the tables and all will come
out
OK? ALso, I need to keep all the customer tables in the db because any
customer might come back later with an additional request or need to fix
something and I don't really want to go through reimporting that data from
excel.

I have noticed that when I change the name of a table that a query uses,
it
seems to propagate through the query, so I'm concerned that when I change
the
name back from table1 to table1CustA, that might screw things up for the
next
customer.

Thanks.
--
Alan



.

Quantcast