G
Guest
Well, I still don't know what the problem is, but I came
up with another solution. One of the tables in the SQL -
tblUsageLocation - only had a few records in it. So I
created a new table with similar information.
Using this new table in the SQL causes it to run as I
expected. So there is some setting in my DB that is
causing the gremlin. I'll have to track that down later.
-dch
up with another solution. One of the tables in the SQL -
tblUsageLocation - only had a few records in it. So I
created a new table with similar information.
Using this new table in the SQL causes it to run as I
expected. So there is some setting in my DB that is
causing the gremlin. I'll have to track that down later.
-dch