G
Guest
I am working on upsizing our MS Access application to an adp. On only one of
the forms am I having problems: I can update and delete records, but when I
try to insert a record, I get this message:
Invalid input parameter values. Check the status values for detail.
I not been able to isolate it when debugging, and running profiler I do not
see any insert command coming across the wire. This makes it very difficult
to troubleshoot! I did step through debugging, and on the last line that
executes before the error occurs (exit proc) I examined each of the fields in
the recordset. Using those values, I created an insert command and was able
to perform the insert through management studio.
I have found references to this error elsewhere on the web, but no
solutions. Can someone help?
Client: Access 2003/SP2 on Windows Server 2003 Standard/SP2
Server: SQL Server 2005/SP2 Developer Edition (9.00.3042.00) on Windows
Server 2003 Standard/SP2
UniqueTable and Resync properties are set, and the unique table's primary
key (an identity column) is included in the dataset. I'm not completely
certain, but I think that it worked until we moved it to SQL 2005. Database
is running in 9.0 compatibility mode, but changing it back to 8.0 didn't seem
to help.
TIA,
Joel
the forms am I having problems: I can update and delete records, but when I
try to insert a record, I get this message:
Invalid input parameter values. Check the status values for detail.
I not been able to isolate it when debugging, and running profiler I do not
see any insert command coming across the wire. This makes it very difficult
to troubleshoot! I did step through debugging, and on the last line that
executes before the error occurs (exit proc) I examined each of the fields in
the recordset. Using those values, I created an insert command and was able
to perform the insert through management studio.
I have found references to this error elsewhere on the web, but no
solutions. Can someone help?
Client: Access 2003/SP2 on Windows Server 2003 Standard/SP2
Server: SQL Server 2005/SP2 Developer Edition (9.00.3042.00) on Windows
Server 2003 Standard/SP2
UniqueTable and Resync properties are set, and the unique table's primary
key (an identity column) is included in the dataset. I'm not completely
certain, but I think that it worked until we moved it to SQL 2005. Database
is running in 9.0 compatibility mode, but changing it back to 8.0 didn't seem
to help.
TIA,
Joel