Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
PanzerAttack
Yak Posting Veteran
71 Posts |
 Posted - 2011-09-05 : 11:23:02
|
| Grrr I'm stuc again, I've done this a dozen times but it doesn't seem to like this table.This works:CONVERT (varchar(10), dbo.T003_Trade_Reporting.ImportDate, 121)This doesn't:CONVERT (varchar(10), dbo.T005_Actual_vs_Accruals.ImportDate, 121)I get the error:The Multi part identifier "T005_Actual_vs_Accruals.ImportDate" Could not be boundI can't see what the difference is. |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2011-09-05 : 11:48:27
|
| Well, without seeing the rest of the query we cannot see it either. You appear to be using a deprecated method for referencing your columns and changing to using an alias will probably clear this up.My guess is that you do not have the table 'T005_Actual_vs_Accruals' included in the FROM clause of the query. But, that is just a guess at this point.Jeff |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2011-09-06 : 04:56:29
|
| might be that you've wrapped your query inside a derived table where this column is coming and then trying to reference it using original name. if you've different alias for derived table use <alias>.ImportDate rather than T005_Actual_vs_Accruals.ImportDatealso i cant understand why you're converting dates to varchar. this is not a good approach unless you dont have a way to do this at your front end. just remember that by making date values varchar you're making date manipulations difficult and also doing lot of unnecessary convertions------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
|
|
|
The Multi part identifier Could not be bound