Data Import Best Practices

  • Thread starter Thread starter Jim Shaw
  • Start date Start date
J

Jim Shaw

BlankContext Access 2002 in an *.mde format

My client receives an annual Excel workbook from Corporate HQ. It contains
Payroll Compensation increases for the whole staff of my client's
organization. We need to import this data into my application safely and
accurately, but my client does not control the format of the Excel file
received. Therefore, my client will need to cut and paste into a new sheet
before importing. I'm just getting ready to design the logic for this, but
I'm interested in everyone's thoughts on how to make this logic bullet
proof. My client will not have access to tables, queries or any of the
power user tools. They will work only thru functions activated on the
switchboard.

What "best practices" do you recommend for this?

Thanks for sharing your experience
Jim
 
BlankContext Access 2002 in an *.mde format
My client receives an annual Excel workbook from Corporate HQ. It
contains
Payroll Compensation increases for the whole staff of my client's
organization. We need to import this data into my application safely and
accurately, but my client does not control the format of the Excel file
received. Therefore, my client will need to cut and paste into a new
sheet
before importing. I'm just getting ready to design the logic for this,
but
I'm interested in everyone's thoughts on how to make this logic bullet
proof. My client will not have access to tables, queries or any of the
power user tools. They will work only thru functions activated on the
switchboard.

What "best practices" do you recommend for this?
Click to expand...

unless you want to use adox to rewrite data junction ...
you get create an import app based on a static table that your client can
scrub his spreadsheet into.
sounds like he knows how to cut and paste...
 
Back
Top