1 Reply by charliebarnes

  • charliebarnes
  • Veteran
  • Offline
  • From: Greater Lincolnshire
  • Registered: 07-09-2008
  • Posts: 1,396

Re: The INSERT INTO statement contains the following unknown field name

Exception path:
EOleException : The INSERT INTO statement contains the following unknown
field name: 'External_Filename'.  Make sure you have typed the name
correctly, and try the operation again
EDBMergerError : Error occurred transferring records for
SQLSERVER_LOCATION_BOUNDARY into the main database
EDBMergerError : Error occurred transferring records for
SQLSERVER_LOCATION_BOUNDARY into the main database

Any ideas?

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

charliebarnes's Website

2 Reply by johnvanbreda

  • johnvanbreda
  • Administrator
  • Offline
  • From: UK
  • Registered: 27-04-2006
  • Posts: 1,237

Re: The INSERT INTO statement contains the following unknown field name

Hi Charlie
Are you able to check that your LOCATION_BOUNDARY table has a column called External_Filename? If not, it sounds like you have had a problem with an upgrade completing at some point.

Best Wishes

John van Breda
Biodiverse IT

johnvanbreda's Website

3 Reply by charliebarnes

  • charliebarnes
  • Veteran
  • Offline
  • From: Greater Lincolnshire
  • Registered: 07-09-2008
  • Posts: 1,396

Re: The INSERT INTO statement contains the following unknown field name

Whoops, something went missing from that post.

I meant to add this occurs during a Recorder import (zipped access) from one installation to another. It seems to be importing some records fine, but then this error pops up.

John, presumably this is a problem on the target computer - could it be a problem with version differences?

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

charliebarnes's Website

4 Reply by johnvanbreda

  • johnvanbreda
  • Administrator
  • Offline
  • From: UK
  • Registered: 27-04-2006
  • Posts: 1,237

Re: The INSERT INTO statement contains the following unknown field name

Good spot Charlie. This was a change in script 0000006E in the upgrade kit, so if you are importing from a updated Recorder into an old one you will get this error. I thought that Recorder now tolerated this sort of thing but apparently not.

John van Breda
Biodiverse IT

johnvanbreda's Website