D
Dale
I have an application that works fine when I run it on my own client,
but when it is run on a different client the SQL code that is generated
is different.... Let me explain...
I have an access ADP that in one of the reports, it uses a User-defined
function(UDF) as its recordsource. By watching it run using SQL
Profiler, I can see that when I run it on my PC, the SQL code that is
sent to the SQL Server is correct, in that it selects all of the
columns I was expecting it to. When I run it on another machine, the
SQL that is generated is..... "Select 1 from
"dbo"."udf_Author_Mailing"() and not all the columns.
I dont think that the issue is a security thing, as i have tested this
on a machine with a person logged on as an SA, and DBO of the database
I am using, with the same results.
I had them try running the UDF directly, and they are able to run the
UDF and return data correctly. But when they run the report, all it
does is return the word - ERROR#.
If this is not clear, I will try to explain differently if needed.
Dale
but when it is run on a different client the SQL code that is generated
is different.... Let me explain...
I have an access ADP that in one of the reports, it uses a User-defined
function(UDF) as its recordsource. By watching it run using SQL
Profiler, I can see that when I run it on my PC, the SQL code that is
sent to the SQL Server is correct, in that it selects all of the
columns I was expecting it to. When I run it on another machine, the
SQL that is generated is..... "Select 1 from
"dbo"."udf_Author_Mailing"() and not all the columns.
I dont think that the issue is a security thing, as i have tested this
on a machine with a person logged on as an SA, and DBO of the database
I am using, with the same results.
I had them try running the UDF directly, and they are able to run the
UDF and return data correctly. But when they run the report, all it
does is return the word - ERROR#.
If this is not clear, I will try to explain differently if needed.
Dale