REPEAT POSTING - I REALLY NEED HELP

  • Thread starter Thread starter Jerry Iglowitz
  • Start date Start date
J

Jerry Iglowitz

I am repeating this posting as I really need help on it and I got no
responses. Please -I would appreciate any suggestions.

I created a payroll program years ago in Office 97 which used Access
as a front-end for data entry and display, (among other things), but the
work was all done in a fairly huge Excel spreadsheet which contained
employee data, tax tables, and individual records for each payroll
event. This program worked just fine under Windows 98, but when I
updated it to run under Office XP, strange things have been happening.

For one, the update times have slowed to a snail's pace -i.e. several
minutes for each event, and for two, it seems to be generating a new
linked table for each data entry event.

I am not that versed in the programs, but got to where I needed by brute
force, but I would definitely appreciate any help you can give me.
Please keep it as simple as possible, however, as I do not comprehend SQL.

Thanks in advance,

Jerry Iglowitz
 
Do I understand that you're using linked EXCEL files as the data tables for
your ACCESS front end? Such a setup is "notoriously" slow for any type of
data updating, assuming that you are modifying data in the EXCEL files from
the ACCESS front end.

Your post doesn't give us any structural or procedural information about
what the database is doing. But I will suggest / recommend that it's
probably well past time to move the data into ACCESS tables. Do you have the
data in EXCEL because that is how it started? Or is there another reason for
keeping the data in EXCEL?
 
Ken,

First, I must apologize for being so long in getting back to you -I
have been exceedingly busy with my business -to put it mildly.

To answer your question, I tried initially to set us the payroll
program strictly in access, but the built-in functions just weren't
adequate to the task. It's been awhile, but VLookup was one I think. I
have incorporated the tax tables, etc. as well. (I'll send you a copy
if you would care to look at it.) So I built a whole payroll program
in excell, and selected access to serve as a front end only. It worked
very well under Windows 98, and Office 97, but when I moved on to
Windows XP and Office XP, it started generating a new linked table for
each step of data entry. It didn't do this before, but it is now. I'm
not sure I am able to move my base spreadsheet into access at this
point. Any suggestions?

Jerry
 
Any data that are in EXCEL should be capable of being moved into ACCESS,
although the table structure would need to be worked out ahead of time
(which is true for any database application).

VLOOKUP doesn't have an exact counterpart within ACCESS, but there are many
ways that it can be duplicated in ACCESS.

I have not seen the problem you describe with "generating a new linked table
with each data entry". If the EXCEL worksheet is linked to the ACCESS front
end as a "linked table", I would not expect this behavior at all. How do you
interact with the EXCEL files from ACCESS; are you linking to them via code
when you need the data? or do you have links to them via the Tables window
in ACCESS?
 
Back
Top