SQL Stored Procedure Name - Dumb Question

[malcolmt]

It's late in the day and I'm about to go home without an answer to this question.

I hope you can help and I'm sure it will be a simple answer to a dumb question.

I have numerous existing crystal reports (v9) which use MS SQL Server 2000 stored procedures without any problems.

I have just noticed that any new reports I am creating show a number after the stored procedure name in the database expert and then thereafter whenever a column is referenced in the report.

All of my previous reports do not have this number after the procedure name.

This caused an error when i copied some formula code from an old report to a new one as the stored procedure names no longer were the same because of the ;1 at the end of the name.

It is happening on multiple client machines and against multiple SQL servers.

Any clues?

Thanks,

Malcolm.

 

[MisterMo]

If you go on the Set Datasource Location and look at the property of every table or SP, you'll find that they all have a number at the end of their name (at least they do on mine)

To fix the problem of copying formulas between reports, simply name your SP on the new reports to match the names on the old ones.

I always use aliases because the original names are too long and are a real pain when writing formulas



Mo

 

[malcolmt]

Thank you Mo,

I'm sure that will solve my problem.

My sp names are also very long and most of my reports have been based on views, so the numbers at the end of the names did not look familiar.

I think what has happened is that I have previously renamed other sp's inside CR after doing a set datasource location, so the "penny did not drop" when I posted my question.

Malcolm.