Hi Sola,
I ensured that my path and file name both are 100% correct. This unfortunatly didn't change the outcome of my error. I also made sure that I can open the file via this exact filepath.
As for your second recommendation, I made sure the file was in the right format. Comma separated, with a header and my date fields being in the same format as my table in access. Therefore I changed the format property of my date fields in access to "yyyy-"mm"-dd" - without it doing anything sadly. This would have weird anyways, since it used to work with the exact same type of csv file in the same database two weeks earlier. I made sure it's not the issue either way though. I am testing it with a smaller file so any invalid characters would jump my eye.
I tried repairing my database and also tried using a brand new access database with the same results. My colleague suggested it had something to do with my virtual access on the folder. My technicians don't know yet what the problem is, so I am asking you again.
Do you have more ideas what I could try to fix this? I have really no clue what changed. I came back from my hollidays and somehow this bug appeared. The only thing that could have happened in the meantime was my admins updating my system or access loading an update or something.
Thanks for your help and the effort.
Kind regards,
TK