Microsoft Dynamics GP (Archived)

Prototype Procedure showing error "cannot find script" (stored procedure name)

(0) Share

Report

Posted on by Community Member

Hi,

I have created a stored procedure in SQL as below

CREATE PROC dbo.HBM_TestRun1

select * from HBM060 -- custom table

GRANT EXECUTE ON HBM_TestRun1 TO DYNGRP

but when I write prototype procedure in dexterity as below:

sproc returns long Ret_Code;

call sproc "HBM_TestRun1",Ret_Code;

it shows error message "cannot find script HBM_TestRun1"

Till yesterday morning, I am able to call stored procedures perfectly from dexterity

but now I am not able to call any new stored procedure.

I did another activity, to modify (add another parameter) to an existing SP, for which prototype Stored Procedure is working correctly, and surprisingly the prototype procedure compiled successfully without giving error for new parameter. I then add new parameter and it won't compile. Meaning, the dexterity is not able to refresh the db connection.

Can anyone, help me out in resolving this issue.

GP Version is 10 with SP5 (10.00.1579)

Dexterity Version 10.0.332.0

Note: the spelling of SQL procedure and prototype is exactly same (as shown in the above code).

Regards,

Waliullah

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Naga Kiran on at

Like (1)

Report

The possible mistake here would be:

You have created the stored proc for the company database then prototype procedure in Dexterity is under 'System' series . That means company procs should not be listed under 'System' series in Dex.

Similarly System DB stored procedures should be under 'System' series in Dexterity

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Naga,

I already verified that, the stored procedure is created in COMPANY database (TWO) and I am creating prototype procedure in Dexterity under 'Sales' series.

Regards,

Waliullah

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Hi,

first create a Dex procedure HBM_TestRun1 (same name exactly as the Stored procedure name).

and then you need to add the below script, into that dex procedure,

sproc returns long Ret_Code;

call sproc "HBM_TestRun1",Ret_Code;

hope this will work for you,

Regards,

SantoshG

Was this reply helpful? Yes No
Suggested answer

Naga Kiran on at

Like (0)

Report

If you have set the series properly, I suspect your ODBC connection. Do you have multiple SQL Server instances? If so please verify your ODBC connection whether its pointing to the correct SQL server instance where you created the stored procedure.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Santosh, it solved my problem.

Thanks Naga for your reply too.

Regards,

Waliullah

Was this reply helpful? Yes No
Suggested answer

soma 24,410 on at

Like (0)

Report

While compiling the code, Dexterity will through the error message for calling Stored Procedure only if the below conditions.

1. If the Dexterity Procedure Name is not same to Called Stored Procedure name withing the dex script.

Note: Dexterity compiler will not consider whether the stored procedure available or not in the company/system database. See the below screenshot. Here the SP "HBM_TestRun5" is not available in both system and company database. But while compiling the code, dexterity was not showing any error. Because the script name and called SP are same. While running this code within GP, then the GP will through the error. Dexterity not consider this.

2. The input parameter with the dex code is not match with the passed parameters in called stored procedure.

Hope this helps!!!

Was this reply helpful? Yes No