Well, the problem is not related with my code. Even when the wizard import is used a standard table is created always that Access identify a conversion error. I´m trying to avoid the automatic creation of this table of errors. I´m aware of the errors but they don´t matter in my case.
With the automatic creation of the error table, each time an user run a import a new error table will be created and soon I will full of rubbish !
Ok, so what you would have to do is import the data with VBA and have controls in it to handle (ignore) the data conversion errors rather than relying on Access' importing wizards. The wizards are hard-coded to produce those error tables.
Or you could ignore them or delete them after your import completes.
I understood, master. I think I will prefer to try deleting them after the import procedure. I'm not a developer and my skills are very short to try to handle all possible errors in the field conversion.