M
mflex77
I'm relative new to MS Access, using Access 2007, and I'm not too
technical. Having said that, I have a situation in which I'm linking a
text file into the database (5 fields total, 3 are text fields and 2
are long integer fields). Off of that text file, I have a make table
query that copies all the .txt file data into a new table. When I
click on the make table query, I get the following message: "You
cannot record your changes because a value you entered violates the
settings defined for this table or list (for example, a value is less
than the minimum or greater than the maximum). Correct the error and
try again."
However, when I compact and repair the database after getting the
message and then run the query, the table is able to get created. This
led me to think that perhaps the .txt file was corrupted, but it's
happening for other text files that have a non-text fields. None of
the values for the non-text fields seem to be wrong or unusual.
Does anyone know what might be going on? It'd be great not to have to
compact and repair the database every time I want to run a make table
query with non-text fields.
technical. Having said that, I have a situation in which I'm linking a
text file into the database (5 fields total, 3 are text fields and 2
are long integer fields). Off of that text file, I have a make table
query that copies all the .txt file data into a new table. When I
click on the make table query, I get the following message: "You
cannot record your changes because a value you entered violates the
settings defined for this table or list (for example, a value is less
than the minimum or greater than the maximum). Correct the error and
try again."
However, when I compact and repair the database after getting the
message and then run the query, the table is able to get created. This
led me to think that perhaps the .txt file was corrupted, but it's
happening for other text files that have a non-text fields. None of
the values for the non-text fields seem to be wrong or unusual.
Does anyone know what might be going on? It'd be great not to have to
compact and repair the database every time I want to run a make table
query with non-text fields.