Viewing 15 posts - 40,861 through 40,875 (of 59,069 total)
Hmmmm... thinking about it a bit more, the tables may actually be identical for column names. If that's true, I don't need the CREATE statement... just confirmation that's true.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 1:06 pm
I believe I may have it figured... I just need some confirmation... any chance of you posting the CREATE TABLE (or whatever) from ACCESS for the Date_3 table (I think...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2009 at 1:04 pm
Must be a different query. The output you've shown returns 19 columns... the query you've shown returns only 7. Not to worry, though... I think I have it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 11:27 pm
If knowledge about ACCESS were gasoline, I wouldn't have enough to run a sugar-ant's mini-bike through a match box. With that in mind, thanks for posting the tables... I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 8:34 pm
sqlbuddy123 (12/1/2009)
Also instead of getting the output in the Command window, can we export the results to a file.
Sometimes, the "old ways" are the easiest...
[font="Arial Black"]OSQL.exe -L >C:\Temp\MyServers.txt[/font]
... and be...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 8:16 pm
CirquedeSQLeil (12/1/2009)
Sorry Jeff - did I give any answers away?
Yep... just in time, too. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 7:35 pm
I can give it a try but a little more info would help me a lot... any chance you could post the CREATE TABLE statements for the Data_3 and SKU_CONTENTS...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 7:23 pm
incercare0 (11/30/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 7:03 pm
I went through something similar once. I was "lucky" (waiting for the opportunity to strike, actually :-D) because I also had the foresight to not only keep track of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 6:44 pm
John Waclawski (12/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 6:16 pm
tknight (12/1/2009)
set @StartDate= dateadd(hh,12,cast(convert(datetime,@Start_Date,101) as...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 6:10 pm
mvertommen (12/1/2009)
Thank you for quick response.
I don't have an actualy example as this is just "research" right now.
I do know how to create the join in order to get...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 5:53 pm
Agreed... SYNONYMs are great. If you can't use them for some reason, a "pass through" view will do the same wonderful thing except instead of ALTER SYNONYM, you would...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 5:49 pm
Not a problem...
Change this...
print @sql
... to this...
EXEC (@SQL)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 5:45 pm
Test-170228 (12/1/2009)
PARAMETERS SQLPeriodIndex Text ( 255 ), theMarket Text ( 255 ),...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 1, 2009 at 5:35 pm
Viewing 15 posts - 40,861 through 40,875 (of 59,069 total)