Phantom SQL

[Vic]

Have you ever had a strategy that has only one DB object yet when run would issue two different SQLs?

I know it is very hard to believe but this is exactly what is happening! And we are not talking about the same SQL executed twice. We are talking about an older version of DB Lookup SQL that used ot exist before being replaced by a new one suddenly being brought back to life, even though it is nowehere in the strategy itself!!!

I had a SELECT statement in my strategy which I later replaced by PROCEDURE and you have guessed it, I have both SELECT and PROCEDURE executed by URS even though I can only see PROCEDURE in the strategy now. I tried deleting DB object, and recreating it, but it would not go away. Now I am forced to recreate the whole strategy!

6.5.101.04 is the version.

Anyone else?

[Timmy2000]

It has to do with part of your strategy being corrupted after you tried to compile the code with tablename containing a dot.
I had a similar problem before and had to redo everything from scratch.

[Tony Tillyer]

Vic,

Similar to the last reply, you may now be referring to a .dbo Table, rather than a .genesys Table from within SQL. Check out the Table Names and Owners in SQL.

Tony