Rob,
Happy to help. But I have some questions.
You said "I have downloaded, unzipped and run it without changing anything apart from the file path and name for the full matches csv file."
Did you run the routine using TableW and your test version of the csv that had 35 records? That test was to ensure the logic was working as expected/required. TableW has the same structure as your Matches. This is really a "proof of concept/logic". Always test on a copy of the data.
The error 94 with the full version of your csv and Matches could be a bad record(s)/format in the incoming csv file- could be no Date supplied, so conversion would fail.
If you import the csv file into an empty table of the same structure as "W", you could
==run a query to see if all Date values are present and/or flag any that are invalid. Then review any invalids before moving to do the conversion/update.
==Another option is to adjust the ImportMatches to check for any invalid/valid entries in Date when doing the conversion.
Do you still have a copy of the csv file and the Matches before you ran the update?
Let's find and resolve the source of the error.
In the table where you import the Matches csv data, you can run this query to identify any records where there is no Date field value.
Change the "W" to the table in which you import the full csv.
Go to create query; SQL view; then paste this code; run t and let us know the result.
Code:
SELECT
ID
, matchId
, League
, Season
, Date
, convDate
, startTime
FROM w
WHERE Date Is Null;
I removed the Date from 1 record(ID 1213991) in the test csv and ran the query.
Result was
Code:
ID |
matchId |
League |
Season |
Date |
convDate |
startTime |
1213991 |
1203676 |
Ireland tour of West Indies 2019/20 |
2019/20 |
|
|
13 |
Good luck.