Subscript out of range access 2000 vs 2007

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi gang,

I have a website that uses an access 2000 db. I have always uploaded a the
same csv file to update it. (There is a upload specification associated with
the db). It has always worked fine. I have just switched to Office 2007.
Access 2007 gives me the famous "Subscript out of range error". When I use a
different system running Access 2000 it works just fine (using the same csv
file!!).

PS is it too much to ask Microsoft to REQUIRE a programs help system to have
at least 1 sentence that explains every error message? There is NO reference
to this message in the help files for Access 2007. The error could read "Bla
bla bla" for all the help it provides.
 
JFD said:
Hi gang,

I have a website that uses an access 2000 db. I have always uploaded a the
same csv file to update it. (There is a upload specification associated with
the db). It has always worked fine. I have just switched to Office 2007.
Access 2007 gives me the famous "Subscript out of range error". When I use a
different system running Access 2000 it works just fine (using the same csv
file!!).

PS is it too much to ask Microsoft to REQUIRE a programs help system to have
at least 1 sentence that explains every error message? There is NO reference
to this message in the help files for Access 2007. The error could read "Bla
bla bla" for all the help it provides.

The error probably indicates that you have a one-over error. My guess is
that the Import Specification under A2007 does not align with the .csv
file and the .csv file has more comma-separated values than the number
of fields defined in the import spec.

I'd start there. Perhaps the migration to A2007 caused an update to some
part of the Import Specification so I would carefully compare the Import
Specification between the two versions.

If there is any code involved in this import process then that would
need to be checked as well. Let us know what happens.

--
'--------------------------
' John Mishefske
' UtterAccess Editor
' 2007 Microsoft Access MVP
'--------------------------
 
Thank you for your response.

The file has many commas in the text fields. The text fields are enclosed
in quotations to eliminate this issue. The File looks fine in Excel.

Is anyone aware of a utility to debug these types of errors? Is there a way
to force Access 2007 to emulate Access 2000?

Is it possible to load Access 2003 onto a system with Access 2007 already
installed without causing more grief.

I guess I should have stayed with the previous version of office.
 
I just visited UtterAccess and joined. Nice site but I couldn't file a link
to create a new topic/message. I'm looking to hire a consultant for an hour
or 2 of "gotomeeting" to troubleshoot this issue with me. Willing to pay
the going rate for an MVP.
 
Back
Top