invalid argument while importing one object from one db to another

[Leo_Polla_Psemata]

Hi There
I am trying to transfer two objects in my new database for 2022, while many other objects have been transferred without hassle,
there are two tables that i get invalid argument, i tried to transfer in another testing db, same problem ?!
What could be wrong ?

Now I will recreate from scratch these two tables but i wonder if this rings any bell to you.

 

[theDBguy]

Do you still get the same error if you only import the table structure (without the data)?

 

[Pat Hartman]

You may have a corrupted record or index. Try compact & repair. If that doesn't fix the problem, try exporting the data to a csv and then using theDBguy's suggestion to import only the schema for the table. Then you can import the data from the csv file.

 

[Leo_Polla_Psemata]

You may have a corrupted record or index. Try compact & repair. If that doesn't fix the problem, try exporting the data to a csv and then using theDBguy's suggestion to import only the schema for the table. Then you can import the data from the csv file.

Hi, very strange
I have recreated the tables in my new db from scratch, but, just for the history,
i tried repair compact, no import, i tried without data, nothing, i removed all records from source db, again invalid argument

 

[Pat Hartman]

OK, but did you do what I said to do? Did you use the EXPORT function?

 

[The_Doc_Man]

Do you have a computed field in the tables that are giving you trouble? Or a Multi-Valued Field?

 

[sonic8]

What could be wrong ?

@Leo_Polla_Psemata, can you please check and confirm if there is any column with Attachment data type in the table?
Which version of Access are you using? (If Access 365, please state the exact Version and Build as displayed in "File"-"Account")
I suspect this might be caused by a new bug in the most recent releases of Access.

 

[Leo_Polla_Psemata]

@Leo_Polla_Psemata, can you please check and confirm if there is any column with Attachment data type in the table?
Which version of Access are you using? (If Access 365, please state the exact Version and Build as displayed in "File"-"Account")
I suspect this might be caused by a new bug in the most recent releases of Access.

Hi, no multiple value fields but "with Attachment" which i haven't used, maybe there is one pdf somewhere, i will check .
It is my application at home pc which oi office 19, i ll chack the exact version. I ll try to remove the attachment field and chack again.

 

[Leo_Polla_Psemata]

OK, but did you do what I said to do? Did you use the EXPORT function?

Yes i have, i have removed the entire data and tried to "import" , no way , i think the problem must be the "with attachment" record because same problem was encountered in another two tables that were "with attachment" field.

 

[Pat Hartman]

Ah ha. The attachment field is an ACE/SharePoint structure and is incompatible with all other relational databases which is why experts suggest not using it. When MS adds stuff like this to Access, it doesn't necessarily make it compatible in all the places where they need to.

 

[shanegroff]

Hi There
I am trying to transfer two objects in my new database for 2022, while many other objects have been transferred without hassle,
there are two tables that i get invalid argument, i tried to transfer in another testing db, same problem ?!
What could be wrong ?

Can you try restarting Access, then try this again?

 

[shanegroff]

Ah ha. The attachment field is an ACE/SharePoint structure and is incompatible with all other relational databases which is why experts suggest not using it. When MS adds stuff like this to Access, it doesn't necessarily make it compatible in all the places where they need to.

Attachment fields will also represent File/Image columns in Dataverse. In any case, though, you should certainly be able to import a table from one Access database into another, regardless of what field types you have. This is a bug (but should be fixed now)

 

[Leo_Polla_Psemata]

Indeed the problem was the nature of one field (attachment), after i removed this field from source db, the table was transferred to new one at "tsak bam" mode