1

Topic: Error importing data

I am having problems transferring a dataset from my office copy of Recorder (v6.23) to a local recorder (v6.22) I don't know if the different versions is significant!

Export format: NBN Access Database (.zip)
Reassign Custodianship: false

The error message is basically:
"Error occurred transferring records for SQLSERVER_SAMPLE into the main database"

The full report is attached

Craig

Post's attachments

Error-73570442298302.txt 31.28 kb, 5 downloads since 2015-04-16 

You don't have the permssions to download the attachments of this post.
Craig Slawson
Staffordshire Ecological Record

2

Re: Error importing data

It may be the new Private Location fields which are causing the problem. I will check.

Mike Weideli

3

Re: Error importing data

The new fields are included and probably cause the problem.  As they should  always be blank it may be possible to drop the fields during export, however, this will may cause problems with importing the data   unto a 6.23 version of  R6.

Mike Weideli

4 (edited by ser 24-04-2015 06:36:27)

Re: Error importing data

Thanks Mike,

Are you able to produce a bug-fix for this as it isn't good for this level of incompatibility within Recorder

Craig

Craig Slawson
Staffordshire Ecological Record

5

Re: Error importing data

Hi Mike

We have just encountered this error when sharing some of our records, using zipped NBN format with one of our Recorder 6 users...
Error occurred transferring records SQLSERVER_SAMPLE" into the main database.
I can ask for the full error report if needed.

Just wondering if you produced a fix for Craig?

Many thanks

Pauline

6

Re: Error importing data

Please can I have some views on what we should do about this issue

What we have been trying to so is to ensure that you can import from an older version of the database, but  we haven't been attempting to allow export from a newer version to an older version. In this specific instance the problem is caused by the two new private  fields in the  Sample table. I had assumed we would be able to solve this by always excluding these field from the export. but there is now a request to make the export of these fields optionally so always excluding them is no longer an option.

Maintaining backward compatibility so that newer version of R6 can export to earlier version requires some major changes somewhere. The uses of  resources on this is questionable for two reasons. Firstly, the problem can be solved by getting the  receiving system to upgrade, which is not a complicated process. Secondly, there may be situation where we can not maintain the compatibility - for example if the length or data type of a field is changed.

Mike Weideli

7

Re: Error importing data

Mike -

MikeWeideli wrote:

Firstly, the problem can be solved by getting the  receiving system to upgrade, which is not a complicated process

I agree. Given limited resources, this shouldn't be a priority (sorry Craig!). IMHO given that updates do more than add functionality (i.e. fix bugs), all Recorder 6 systems should be up to date.

Can't the export be manually edited to remove these columns?

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

8

Re: Error importing data

Yes, but you need to unzip the file, remove the columns in Access and zip the file.

Mike Weideli