"Value too long" Error

[Kristimar]

Well, I’m deflated. I’d appreciate help, or a hint.

The form based on my main table is spitting back this error whenever I try to save a record, and it seems to affect ALL my fields:

(Sorry - I’m working in Spanish, but the error itself is in English).

I’ve tried adjusting the allowed field lengths - in the form, in the table… (after searching the forums)… No luck. I also created a new form using the Wizard. Same problem.

I’m attaching the database file, if any kind soul cares to take a look.

Thanks so much, in advance. (I’m quite a newbie - started two weeks ago… Now I’ve hit a brick wall.)

Actividad de formación - gestión documental.V10.odb (412.6 KB)

Edited to add: Base v.7.3 - Windows 10

[Hrbrgr]

You must specify for the respective ID in the tables for Auto value=Yes. The key is assigned correctly.
Example: tbl-00_Actividad_inicial → ID-Curso_GIFP

The “Sub”-IDs should IMHO be created as INTEGER.

---

English documentation

[mikekaganski]

@Hrbrgr: please stop closing questions. We only need answered questions, not closed. You prevent others from answering, offering new possible solutions, without any benefit.

We already had a discussion on the older site, when another user had a habit of closing questions without need; I don’t recall prominent contributors wanting questions closed.

[Hrbrgr]

@mikekaganski ,

OP wrote:

(Easy to fix by going into the table / field in question and changing that setting).

---

But it should not be a problem not to close.

[Kristimar]

Solving my own problem… without really knowing why/how, but:

When I reopened the file I’d sent in the previous message, and tested saving a record again, I was hit with new errors. First, and easiest: one of my fields was set as “mandatory”, and I hadn’t set any default value, so… New Error having to do with trying to save a “NULL” field. (Easy to fix by going into the table / field in question and changing that setting).

The second New Error looked like this:

.

Here, the issue seemed to be that I had set up a 1:1 relationship between my main table and another one, linking both of their Primary Keys. Bad idea - I guess… (this is me, trying to make sense of it)… because while the Primary Key was being created in the Main table, it didn’t exist yet in the other table (??). That is: it wasn’t “matching” anything…? So… Error. I guess.

Solution: I eliminated the relationship between these two tables. (I’ll try to figure out how to fix it at a later date).

After this: ALL the problems were gone. Including the original “value too long” error…(!!). I have no clue why. But there you go.

Attaching the “fixed” file in case anyone is curious.
Actividad de formación - gestión documental.V11.odb (412.6 KB)