T
TerryM
Ok, here's my issue.
I have a rather complicated process, at least I think it's complicated: This
is all run at startup of a Access 2003 DB file that I am hoping to upgrade
to a SQL 2005 Database.
This part is done in Excel using VBA code It downloads a .txt file from the
internet and parses out about 112 rows and 4 columns of data out of about
7000 rows and 10 columns in excel, it then pastes the parsed rows to a new
excel workbook and saves the file as temp.xls and then closes the Excel
application.
MS Access: It then does a docmd.import statement to import the parsed
information from the temp.xls file. Oh, I forgot to mention that the areas
in the txt file that are parsed out are 2 named ranges that are named in the
VBA code in an excel macro. Back to my problem, when I import the Excel
Worksheet (A1112) it imports (A2112). Also sometimes it doesn't import
all the rows. I might only get half of them. But it never imports the first
row at all. Why is it doing this?
I have a rather complicated process, at least I think it's complicated: This
is all run at startup of a Access 2003 DB file that I am hoping to upgrade
to a SQL 2005 Database.
This part is done in Excel using VBA code It downloads a .txt file from the
internet and parses out about 112 rows and 4 columns of data out of about
7000 rows and 10 columns in excel, it then pastes the parsed rows to a new
excel workbook and saves the file as temp.xls and then closes the Excel
application.
MS Access: It then does a docmd.import statement to import the parsed
information from the temp.xls file. Oh, I forgot to mention that the areas
in the txt file that are parsed out are 2 named ranges that are named in the
VBA code in an excel macro. Back to my problem, when I import the Excel
Worksheet (A1112) it imports (A2112). Also sometimes it doesn't import
all the rows. I might only get half of them. But it never imports the first
row at all. Why is it doing this?