H
Herb
Hello All,
I have an ADP that utilizes SQL Server and many stored procedures that was
running under MS Access 2000 just fine.
A report in Access that uses a sproc as it's recordsource and the Input
Parameter property of the report which did work under Access 200 is now
failing after converting the project to Access 2003.
The input parameter property is: @ToteKey =
[Forms]![frmBookCheckout]![frmBookCheckoutSub]![txtToteKey]
If I run the sproc alone and manually enter the totekey value, it works
fine. When the report is executed it says that that there are no records
found!
Right now I have it rigged so that the user can simply type in the totkey
value, since it displays on the form already. But I'd like to get back to
where it just works.
Does anyone know what might have changed in Access 2003 to cause this?
Thanks in advance for any help.
Herb
I have an ADP that utilizes SQL Server and many stored procedures that was
running under MS Access 2000 just fine.
A report in Access that uses a sproc as it's recordsource and the Input
Parameter property of the report which did work under Access 200 is now
failing after converting the project to Access 2003.
The input parameter property is: @ToteKey =
[Forms]![frmBookCheckout]![frmBookCheckoutSub]![txtToteKey]
If I run the sproc alone and manually enter the totekey value, it works
fine. When the report is executed it says that that there are no records
found!
Right now I have it rigged so that the user can simply type in the totkey
value, since it displays on the form already. But I'd like to get back to
where it just works.
Does anyone know what might have changed in Access 2003 to cause this?
Thanks in advance for any help.
Herb