Database

I would use you solution but with a slight change. I would include all columns common to Client and lawyer in the user class. i.e First, Last. If there are few columns that are different for Client and Lawyer, I would just role everything up to User, and allow nulls for those columns which don't apply to both client and lawyer. You will need some business rules to determine when those null fields should have a value.

You could look at the constaints on the foreign key. Does it allow duplicates, does it allow nulls?

Gaaaah, I finally found the cause of the problem. I apparently created my original sproc with "SET ANSI_NULLS OFF". By default queries in management studio runs with ANSI_NULLS ON. DOH![^] For a simple example of the sproc I was playing with: create PROCEDURE [dbo].[Bob_Test] @MaterialNumber varchar(18) AS DECLARE @Replace varchar(18) SELECT @MaterialNumber IF (@Replace != '') SET @MaterialNumber = @Replace SELECT @MaterialNumber When I call this with ANSI_NULLS OFF Bob_Test '123456' my results show 123456 from the first select in the sproc, and NULL for the select after the if statement. With ANSI_NULLS ON both selects return 123456. My faith SQL Server has been restored. Tune in next week for more inept coding... :cool: Kill some time, play my game Hop Cheops[^]

You could use SELECT Col1.T1, Col2.T1, Col3.T1 FROM table1 T1 join table2 T2 ON T1.Col1=Coln.T2 OR SELECT Col1.T1, Col2.T1, Col3.T1 FROM table1 T1 WHERE COL1 in (SELECT Col1 FROM table 2 where Coln=something1 and colm=somethingelse and yadayada)

I would migrate to .net and make it DB agnostic using DBProviderFactories[^]. Then you can choose your poison in the app.config section. Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions

Thank you very much Be Happy

u can use BULKinsert

select * from table1 where SUBSTRING(table1.column2,1,2) like '%@param1%' or SUBSTRING(table1.column2,1,2)>'%@param2%' use dynamic query

yap it will work

Remove the NOLOCK; the insert is messing up some reads. Bastard Programmer from Hell :suss:

Eddy Vluggen wrote: Why is there a commit, if you are only selecting records? Just to be sure that he is committed to selecting records only. Nothing else! :)

Solved the issue. Parameters can be specified that don't show up in the list of preview items. If these parameters are returned (the IF conditions are met and the different view is instead displayed) then these parameters have the requisite value, otherwise they don't and aren't applicable. Thank you for the attempts to answer my question but they were all incorrect.

Why would you want to duplicate data this way?

My pleasure, and thanks :)

chuckcan08 wrote: this could will work FTFY :-)

Database Engine Tuning Advisor[^] might be of help.

Create a job that checks the data store where the job is, compare the system date with the job due date, get the email address from the employee table and send the email using SQL mail. The information about jobs can be found using sysobjects and the related sys% tables. You will need to do some research as to where it can be found. Employee information is your problem. Never underestimate the power of human stupidity RAH

One idea could be do to disable all relations/checks/constraints on the report tables, execute CDC statements and then re enable relations/checks/constraints. Your execution should handle errors nicely though for this to work. Shreekar

unclejimbob wrote: I can't ever recall anyone suggesting that 2 lines of code (delete/reseed) is somehow better than 1 (truncate) and yes, I've been at this game at least as long as you have. Hopefully that statement is flippant. There are in fact differences between using delete and truncate, especially in SQL Server, which have nothing to do with this discussion. And those differences are the reasons is should be used with care and why it is seldom needed. Choosing the correct one has nothing to do with the number of lines. And there is very little in programmng that should be based solely on line count. (It isn't even a good developer productivity metric.) unclejimbob wrote: Indidivuals who come in after the fact and attempt to rate your contribution based upon their own close-enough-is-good-enough two-second evaluation are, of course, putting you down - don't accept it This site is set up specifically to allow rating answers. Especially on technical questions. That is what the "Rate this message" is for. And one need not even explain why they give it a good or bad rating. Moreover I think that any technical site that doesn't allow and expect discourse on the correctness of answers is probably worthless.