Share via

Syntax Error in UPDATE statement

Anonymous
2020-01-16T16:04:46+00:00

Hi,

I am trying to upload a text file via the import wizard to Access, Usually I follow the steps and import is successful but as soon as I click on the file in my explorer I get the spinning cog for a few seconds and then the error message.

I have googled it and cant seem to find the solution, usually happens to folks when writing their own SQL code,

Any help would be great.  I am using MSAccess2003 and my colleague MSAccess2010 and both of us are having the same issue,

Many Thanks in Advance

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

10 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-01-16T19:57:25+00:00

    Hmm, I've imported so large files so not sure size is an issue.  If these files you are trying to import are from and external source they may contain *hidden* characters that are causing the problem.  So may not *see* what the problem is.

    What I do when an import fails and it's from an external source is open in Excel and save it as an XLS.  This 99% of the time either eliminates the *hidden* characters or exposes them which I can then remove.  I would give that a try and see if that works.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-01-16T18:39:19+00:00

    no to SQL server unfortunately.  I will put my files into SAS and export, I find sometimes that reduces the size significantly.  The joys of DATA :)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-01-16T18:38:05+00:00

    Hi Gina,

    I just tried to import a test file through the wizard and it worked successfully.  Makes me think that it may be the files I am trying to import.  Would size be an issue at this point?

    I have checked the text files for anything that looks odd or funky but to no avail.  I will play around with it  some more and keep trying.

    Thanks for the help

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-01-16T18:26:05+00:00

    Hmm, I thought if you were importing a file created in a later version of say Excel that could have been the cause.  I was also thinking you were *not* using the wizard and perhaps some code was *breaking*.  Judging by your replies my thinking was wrong on both counts.

    Wondering if the wizard has become corrupt.  If you create a simple Excel (XLS) worksheet and try to import do you get the same error?

    Was this answer helpful?

    0 comments
  5. Tom van Stiphout 40,211 Reputation points MVP Volunteer Moderator
    2020-01-16T18:21:19+00:00

    There is a new bug introduced with latest release of Office 365 and Office 2016. This is perhaps related. Everyone is scrambling to find out more, so keep looking for updates in this forum from time to time.

    Do you have a SQL Server back-end?

    If yes, does the table you're importing into have an Identity column?

    Was this answer helpful?

    0 comments