D
Dave
I upsized an old Access database to an ADP project. I am using Access 2003
w/SQL Server 2000.
I am having difficulty trying to modify my forms to use the stored procs in
SQL Server.
For example, it appears that the ability to open a form to a specific record
will not work if the form's record source is a stored proc. For example, if
you create a command button, the wizard will walk you through the process of
having the click event open a form to a specific record. This works fine
under native Access DAO but if the record source of the opened form is now a
stored proc, it does not work (even if the proc takes the record id as an
input parameter.)
Can someone conform this is so and whether there is a work around?
Also, when I specify a stored proc with multiple input parameters as the
record source for a form, I am prompted in Access for each of the input
params each time the form opens (even though the params are optional and I
do not need to specify them when calling the proc from other apps).
Besides writting a new proc or coding each input param with a NULL value, is
there any work around for this?
w/SQL Server 2000.
I am having difficulty trying to modify my forms to use the stored procs in
SQL Server.
For example, it appears that the ability to open a form to a specific record
will not work if the form's record source is a stored proc. For example, if
you create a command button, the wizard will walk you through the process of
having the click event open a form to a specific record. This works fine
under native Access DAO but if the record source of the opened form is now a
stored proc, it does not work (even if the proc takes the record id as an
input parameter.)
Can someone conform this is so and whether there is a work around?
Also, when I specify a stored proc with multiple input parameters as the
record source for a form, I am prompted in Access for each of the input
params each time the form opens (even though the params are optional and I
do not need to specify them when calling the proc from other apps).
Besides writting a new proc or coding each input param with a NULL value, is
there any work around for this?