Book a Demo

Author Topic: Transfer Error  (Read 3382 times)

James Chan

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Transfer Error
« on: March 05, 2010, 06:41:49 pm »
Does anybody know how to deal with this error:An error has occurred: DAO.Field[3163]
The field is too small to accept the amount of data you attempt to add. Try inserting or pasting less data ......


Above happened as i transfered data from DBMS to EAP which  created by new project operation.
« Last Edit: March 05, 2010, 06:42:49 pm by c18864 »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Transfer Error
« Reply #1 on: March 05, 2010, 07:39:03 pm »
I've had that issue too.
It is due to a difference in lenght between columns in the access database and the dbms database.

What you can do:
Check on which part of the transfer you get this error. That should give you an indication of which table to look for.
Try also the dbError.txt in the application folder to find if there is more information logged there.
If you know which table is having the issue try to compare the columns between the access table and the dbms table. I can image there might be differences in the pdata, or notes columns.
Then find out which elements have a too long text in those fields, and adjust the text.

Geert

James Chan

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Transfer Error
« Reply #2 on: March 06, 2010, 04:39:06 pm »
Thanks, Geert.

I think EA should support creating a scaling BASE EAP file for DBMS repository transfering.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Transfer Error
« Reply #3 on: March 06, 2010, 10:08:08 pm »
Quote
Thanks, Geert.

I think EA should support creating a scaling BASE EAP file for DBMS repository transferring.
Hi James,

It has nothing to do with scaling per se... The actual defections of the various technologies are inconsistent...

I've developed a set of definitions for both .EAP and MS SQL Server that ARE consistent but that makes them non standard.

So you're left with a  choice - a standard set that doesn't work or a non-standard set that does...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!