Transfer from SQL Server not possible

[ngong]

As usual I am preparing an .eap file with an empty model as a destination for a transfer. It has ~1.6kByte. After starting the transfer in the SQL Server model, I get the failure message "unrecognized database format". The .eap file size is reduced to 0kB, obviously corrupted by the transfer.

What I did just before? I Reset IDs as a measure to another problem.

Now, the model seems to be unusable. Do you know of recommendations to cope with EA in a robust way? What features not to use? One recommendation was not to use EA14, so I stepped back to 13.5. What else?

[Geert Bellekens]

Have you tried starting from a (copy of) a previous backup?

Geert

[ngong]

Thank you Geert.
I tried with a colleague - and he could run a transfer at his installation.
I install new - will give 14.1 a try - and now it works as expected.
Maybe the very long run "Reset IDs" over night and over VPN caused some problem.

[Eve]

As usual I am preparing an .eap file with an empty model as a destination for a transfer. It has ~1.6kByte.

With that size, it's too small to be a valid JET database/eap file.

One recommendation was not to use EA14, so I stepped back to 13.5. What else?

Who gave you that bad advice? With what reason?

[ngong]

Experimenting with checking Jet 4.0 and using the new extension .eapx instead of .eap, now it works.
The minimum .eapx file is - as you said Simon - roughly 2.4 MB.