I work in application support for a large company... We have recently upgraded our operating environment to XP and Access 2002. I have had 3 incidences of Access dbs that are giving errors since moving to 2002.
In all 3 cases, it has been an UPDATE or APPEND query that is run from a form, and the query references controls from the form.
for example:
UPDATE tableX SET tableX.DONE = [forms]![012-WOActvChge]![txtDone]
The error message that I get is:
AppTest didn't update 1 field(s) due to a type conversion failure, 0 records due to key violations, 0 records due to lock violations, and 0 records due to validation rule violations. Do you want to continue running this type of action query anyway?
These are all applications that used to work in the past, so my question is, what has changed between Access 97 and 2002? I have a workaround, which is to code the query in VBA as a string, and place the actual value of the form controls into the SQL then execute the SQL string instead of running a query object. It works, but after doing this in 3 different mdbs, I'm curious as to what is causing this?
Does anyone know?
In all 3 cases, it has been an UPDATE or APPEND query that is run from a form, and the query references controls from the form.
for example:
UPDATE tableX SET tableX.DONE = [forms]![012-WOActvChge]![txtDone]
The error message that I get is:
AppTest didn't update 1 field(s) due to a type conversion failure, 0 records due to key violations, 0 records due to lock violations, and 0 records due to validation rule violations. Do you want to continue running this type of action query anyway?
These are all applications that used to work in the past, so my question is, what has changed between Access 97 and 2002? I have a workaround, which is to code the query in VBA as a string, and place the actual value of the form controls into the SQL then execute the SQL string instead of running a query object. It works, but after doing this in 3 different mdbs, I'm curious as to what is causing this?
Does anyone know?