MS Access Crashes when Importing/Exporting

  • Thread starter Thread starter PJ
  • Start date Start date
P

PJ

Using Access 2003. First time ever having an issues importing/exporting
Excel. Anyone out there encounter this, and if so, what was the solution?
Thanks!
 
Please provide more details about what you're doing as the steps, the
specific information about the EXCEL fie including path and filename, etc.
 
I'm using version 2003, both Excel and Access.

When I want to import, in Access I go to:

File, Get External Data, Import, in the Import Window I change the file type
to Excel or Text (whatever is applicable)...find the file I want to import,
dbl click on it, and then the MS Error Message appears..."Microsoft Office
Access has encountered a problem and needs to close......" "Rapair my open
database and restart...." and finally I get to select whether or not I want
them to send me an error report.

I know that recently IS updated our computers with a MS Office 2007
compatibility extention for Office 2003.

Oh, another thing I can't do is link a List from SharePoint to Access...I've
done this hundreds of times at another company...but can't do it here.
SharePoint goes through the motions all the way to Access...but then Access
stalls. So I don't think it's SharePoint.

Right now, until this is fixed...I'm just using a new blank database on my
local drive, and a tiny test Excel file with a header and a half-dozen rows
of data.

I have Access 97 on the same machine...I'm connected to various office
printers...some people are having the exact same issue...some are not. I
have SharePoint Developer installed and FrontPage. Outside of that, just
typical stuff.

Any suggestions would be greatly appreciated.

Pam
 
My first guess, based on the fact that you have both 97 and 2003 on the same
machine, is that the References in the 2003 file are "messed up" by a
previous use of 97 on the machine.

Try following these steps (from a post by Douglas Steele, MVP):

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

--

Ken Snell
<MS ACCESS MVP>
 
Back
Top