Search results

Definitly helpful, i will keep that set for sure. Thanks for this post!

Usualy if that happen with System DSN it's because you dont have admin rights on the workstation. Placing this in user DSN will make that if another user go on that ws he will not be able to use the ODBC

Thanks for the answer, my solution was simply to create import specification that i use in the macro and it fixed eveything.

The table been created from a first import of the file, there only 2 numeric field formated as Long interger, those 2 field cant excess 8 number in each (restriction from the apps providing the data)

I'm using 2003 version. I think i'm just gonna show users how to use the import wizard since it's also working using that but that make the apps less user friendly than i would.

Hi, I want to import a CSV file into an Access 2003 table. The CSV file have around 53 000 different customer entry. When i do it with the table in the same database, no problem, eveything goes as planned. As soon as i split my database (so the table become linked) and i run the same code, i...

Finaly i found that i can replace the End with Exit Sub and now it work on retail and runtime version. Thanks to everyone! :)

In fact this part seems to go well, i get the messagebox but i think it's the End command that make everything bug since the error occur after the user click OK on msgbox.

I got a database on Access 2003 that work just fine, however i got a problem when user are on the runtime version. Here is the part of my code where it seems to bug. My objective is if the statement is true then i want a message to warn the user with a msg box then stop execution of the code...