Viewing 15 posts - 556 through 570 (of 1,182 total)
Yep, you should have said that. :w00t:
But as far as I know, the answer is "no" you can't do it with EXISTS.
April 8, 2008 at 8:31 pm
Patrick Ige (4/8/2008)
join but keep getting error on the first line
Any ideas..
SELECT stockcode_id,plan_id,mc_id...
April 8, 2008 at 8:27 pm
WRACK (4/8/2008)
Where can I add those functions and stored procedures so they appear everywhere?
In my research I have found that every database is created using the "MODEL" database as a...
April 8, 2008 at 8:22 pm
I would suggest that you study up on JOINS..... 😀
SELECT
A.CustomerID
,A.SurName AS 'CurrentSurName'
,NULL AS 'ArchiveSurName'
FROM
Customer.Customer AS A
...
April 8, 2008 at 7:56 pm
This won't handle the RED records, but it will get you close. 😀
SELECT FIELD_NAME, TABLE_NAME
FROM yourTable
WHERE FIELD_NAME IN (SELECT FIELD_NAME
...
April 8, 2008 at 3:51 pm
Depending on your exact needs, just create linked tables in access. (Right Click - Link ??) in the table tab. Then the data isn't actually moved or copied, but rather...
April 8, 2008 at 1:16 pm
yucky
April 3, 2008 at 12:40 pm
Ihave no experience using it, but wouldn't WITH ENCRYPTION be helpfull?
April 3, 2008 at 11:28 am
1. Swap your tables around the LEFT JOIN clause.
2. Use the OVER .. PARTITION BY like I mentioned earlier...
Create some sample data
DECLARE @project TABLE (project_id CHAR(5), component_id CHAR(5), cost_element_id CHAR(5),...
April 2, 2008 at 11:39 am
It's hard to test without sample data, but I think what you want can be done with windowed functions ...
Specifically, the SUM(...) OVER (PARTITION BY ...)
SELECT
a.project_id...
April 2, 2008 at 10:19 am
1. No, there is no way to do that. OK, Cess shows a way to do it below. But that's a TON of work when you can just not...
April 2, 2008 at 7:55 am
Jeff Moden (4/1/2008)
Antonio...When you say ".RDL", are you talking about a "CLR"?
No, I'll bet he's dynamically creating the .RDL (Reporting Services Definition) files on the fly. 😀
April 2, 2008 at 7:26 am
Create views that expose the data/columns that you want them to "see" and procedures to manipulate it. Then only give permissions to the "customers" on the views and procedures.
April 1, 2008 at 2:46 pm
Viewing 15 posts - 556 through 570 (of 1,182 total)