Problem with parameters in Store Procedures

jalin · Post by **jalin** » Tue 18 Mar 2008 14:56

I was working with MySQL 5.0.27 and updated to 5.1.22. (MyDac 5.20.1.14)

I was working ok but now I have a problem: I cant see the parameters (PARAMS property) of MyStoredProc. When I click on the property the parameters are empty. This is happening with all my store procedures and functions. When I create a new Procedure the resukt is the same: I cant see parameters. I installed again MySQL 5.0.27 and the problem is the same.

What am I missing ?

Thanks
Alejandro

Antaeus · Post by **Antaeus** » Tue 18 Mar 2008 15:35

Please make sure that the Connection property in your TMyStoredProc component is assigned, and the linked connection component is connected to the server (Connected=True).

jalin · Post by **jalin** » Tue 18 Mar 2008 17:01

I have the connection with the DB, I can see the tables, I can see the stores procedures, I can see everything, but I cant see the parameters as I did before

Antaeus · Post by **Antaeus** » Wed 19 Mar 2008 11:50

Please specify some additional information:
- exact version of MyDAC. You can see it in the About sheet of TMyConnection Editor;
- exact version of your IDE;
- do you see the list of stored procedures in the design-time editor on the SQL tab?
- is the command to call the stored procedure generated on the SQL tab in the design-time editor of TMyStoredProc?

jalin · Post by **jalin** » Wed 19 Mar 2008 14:53

- exact version of MyDAC. You can see it in the About sheet of TMyConnection Editor;

5.20.1.14

- do you see the list of stored procedures in the design-time editor on the SQL tab?

Yes

- is the command to call the stored procedure generated on the SQL tab in the design-time editor of TMyStoredProc

Yes, but without parameters.

Before I had the problem, I detected what I think is a bug. I created a Stored Procedure (with MySQL Query Browser) with 4 parameters named:

-xKeySource
-xTranSource
-xKeyResult
-xTransResult

TMyStoredProc detected the procedure and the parameters. Then I changed the name of the parameters in the source code (MySQL Query Browser) such as:

-xKeySource
-xTranSource
-xKeyResult
-xTranResult (without an "s")

and TMyStoredProc didnt detected the new name, I had to change it manually (Text DFM).

So I think there is a bug when you change the name of the parameters.

Alejandro

Antaeus · Post by **Antaeus** » Thu 20 Mar 2008 08:16

I could not reproduce the problem. Please send me a complete small sample at mydac*crlab*com to demonstrate it, including script to create the stored procedure. Also provide the detailed description of the steps to reproduce the problem.

jalin · Post by **jalin** » Fri 21 Mar 2008 05:21

Im going to prepare the sample, but I didnt understand where should I send it ?

Im going to send it next monday because the holy week and I will be in my office next week.

Alejandro

Antaeus · Post by **Antaeus** » Fri 21 Mar 2008 09:45

You should send all information that will be required to reproduce the problem on our side. I suppose that we will need the script to create the stored procedure, a small application that uses this stored procedure, and description of the actions to be performed to reproduce the problem.

jalin · Post by **jalin** » Tue 25 Mar 2008 15:11

I uninstall MySQL and reinstall it. (5.1.22)

I chose the CUSTOM installation and installed all the options. And now, its working ok.

Thanks
Alejandro