[AccessD] Feeding Data into Access from Hundreds of Excel Files with no Common Definition

Arthur Fuller fuller.artful at gmail.com
Wed Feb 26 16:37:13 CST 2014


Gary,

You raise some excellent points. Sometimes I think that developers shirk
their responsibility in lieu of providing "customer satisfaction" or
somesuch, and the result ends in an awkward mess. And I also confess to
sometimes doing it right, despite the client's intentions.

A case in point is what I call "upside down addresses": First thing I ask
for is Country, then region (state or province or canton), and finally
city. That way I can scope each successive dropdown to those that apply,
and also provide the means to add a new city to a region and thence to
country.

Not every app needs such finely-grained table definitions; but on the other
hand, if your firm does business in more than a few countries, this can be
a big help.

Arthur


On Wed, Feb 26, 2014 at 4:22 PM, Gary Kjos <garykjos at gmail.com> wrote:

> I would shift the burden to the sales and marketing people to standardize
> the data. If it's received in the desired format it goes straight in. Have
> any file in a non-standard form sent to them and have them update it to the
> standard. Then they will be a little more willing to kindly ask the
> customers to please use the template provided which really is NOT a burden
> as the customers don't have to think up their own format. Sometimes what we
> think is harder is actually easier. .
>
> GK
>
>
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>



-- 
Arthur


More information about the AccessD mailing list