Access - FORM - vb ends when encounters "#VALUE"

[pod]

Hello
I am importing Excel files data into an Access database. My script goes through one Excel file at a time, row by row, and build a SQL statement for each row to insert data into the database. But on one of the Excel files, it encountered a cell with the value "#VALUE" in it, and the macro stops dead, leaving no debug message, no error popup, it just stops, with Excel file hanging in the process.

Has anyone ever encountered this?

I am using 2003 now, just recently, I am wondering if it is not related.

Thanks

P :oD

[Nathan H]

Hello
I am importing Excel files data into an Access database. My script goes through one Excel file at a time, row by row, and build a SQL statement for each row to insert data into the database. But on one of the Excel files, it encountered a cell with the value "#VALUE" in it, and the macro stops dead, leaving no debug message, no error popup, it just stops, with Excel file hanging in the process.

Has anyone ever encountered this?

I am using 2003 now, just recently, I am wondering if it is not related.

Thanks

P :oD

I've had some issues like that before. I just copied and pasted values in the spreadsheet before import to get rid of calculations and to replace #VALUE and #N/A values with numbers or data.

I didn't have to deal with handling large numbers of spreadsheets or on a repeated cycle, so if that is the case, it would be too time consuming.

What is your code doing in detail?

[pod]

I've had some issues like that before. I just copied and pasted values in the spreadsheet before import to get rid of calculations and to replace #VALUE and #N/A values with numbers or data.

I didn't have to deal with handling large numbers of spreadsheets or on a repeated cycle, so if that is the case, it would be too time consuming.

What is your code doing in detail?

Hi Nathan
... my code reads the data in each cell and builds an INSERT SQL statement, and at the end of each row, the code executes the SQL statement.

I do have many EXCEL files to go through, 308 at a time.

These EXCEL files have MACROS in them, I presume that is where #VALUE came from... but I have been doing this for a few years, I have never encountered this problem before... but this is the first upgrade since then, I was using Access 2000 before