Name change, can't find origin of error

  • Thread starter Thread starter jamesn
  • Start date Start date
J

jamesn

I've recently made a name change on a few database tables. I thought I
got all the name changes done in the front end reference. However,
this one eludes me. I've checked all the classes listed in the error
trace. I've done full text searches across all the documents of the
project and I still can't find a reference to 'ACAllowedMarketCaps'
anywhere.

http://i13.photobucket.com/albums/a291/Reeve04/UnknownError.jpg

Are there any other techniques that people have used to troubleshoot a
problem like this? Or am I missing something in the info displayed on
the error page? Thanks in advance.
 
Note that this is an SQLException i.e. the problem is likely that a SQL
statement that uses this name fails (generally because the object doesn't
exist).

You could use SQL Profiler or check the statements generated in your DB
layer to find out where the statement is generated (could be also perhaps a
view or SP that is broken).
 
I haven't used profiler very much. There are so many options to show.
What options should I enable to see this type of info? Thanks again. :)
 
If the table isn't referenced anywhere in the source, then you probably
forgot to recompile your code.

You can always just hit a breakpoint on that line and debug to see exactly
what is going on.
 
By recompiling do you mean building the solution? I've tried to build
the solution, re-build the solution, and build each individual project
within the solution.
 
By recompiling do you mean building the solution? I've tried to build
the solution, re-build the solution, and build each individual project
within the solution.
 
This doesn't seem like a SQL problem. The invalid object name does not
exist in the database. It is being referenced within the front end.
This may be due to a caching issue. What I really need are some tips
on debugging the front end website.
 
This is why the SQL Server complains. Try to select from a non existant
object in QA and you'll have the same message (also the exception tells this
is a SQL side problem).

Now the next step would be to find out where this SQL statement is
generated... Are you able to catch SQL statements created client side by
your application ?
 
Back
Top