Cannot save the SQL statement of a dataset

  • Hello,

    Could anyone help me with a problem I cannot solve.

    I'am working on a report. I made this yesterday. This morning I changed some and everything was OK.

    Now I want to add a new dataset. I can make it, but when I want to save it nothing is save. Stange enough de dataset name is saved but de SQL statement not.

    Even the datasets in my old report projects cannot be used correctly anymore.

    In short. I cannot save de SQL statement of a dataset anymore. And now I am desperate.

    Thanks if you help me.

    Gery Dirkx

    Nobel

  • You have run into what I call reporting services annoyances, it is not intuitive so I usually just delete the old dataset and manual work the new select statement into the report objects. How? It is like recreating the report because when you make changes to the .sql reporting services does not know, so the changes will not be reflected. Post again if you still need help.

    Kind regards,
    Gift Peddie

  • Hi,

    Thanks for reacting.

    I already did that. Even when I make a new project I have the same problem.

    Any other ideas?

    Gery

  • You can convert it to a stored procedure that takes control from reporting services because all you have to do is point reporting services to the stored procedure in the dataset, so just change command type from Text to stored procedure.

     

    Kind regards,
    Gift Peddie

  • Gift Peddie,

    Thanks for jour answer.

    I can specify the problem now better. It seems that when i use de Generic Query Designer (GQD) the system does not see it as a change to be saved. If i go back to the sql, so stop the GQD, then the system see this as a change to be saved. I always use the GQD. But knowing this at least i can go on with the workaround. I wil sometime reistall the software hopefully everything wil work then.

    Thanks again.

    Gery Dirkx

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply