SQL / ADO / ADO.NET | Forum profile

There is no known problem with using IDENTITY columns. It works well. If you want to really have 'big' numbers, use bigint datatype instead of int. The syntax remains the same.

Jörgen Andersson wrote: Composite indices can on the other hand under certain circumstances considerably speed up a query Ah but I was being derogetry about composite KEYS not indexes. Composite indexes are a basic tool for tuning a database, composite keys annoy me.

Try this declare @t table (sal1 int ,sal2 int ,dur1 int ,dur2 int ) insert into @t select 6 , 7 , 3 , 2 union all select 6 , 7 , 3 , 3 union all select 354 , 867 , 1 , 2 union all select 354 , 867 , 1 , 3 union all select 354 , 872 , 1 , 2 union all select 354 , 872 , 1 , 3 union all select 356 , 867 , 1 , 2 union all select 356 , 867 , 1 , 3 union all select 356 , 872 , 1 , 2 union all select 356 , 872 , 1 , 3 select * from @t I am taking...

I thought the ABS function might be a shortcut, in that it accomplishes the same thing as squaring when you want only the distance between two values, regardless of which is smaller. My main consideration was that the example you gave did not return a distance from the target of 30, only reorders the table. Now that I reread your response, I see that the value I was reading as a single variable (news_id-10) is actually (new_id - 10)....

You need a Configuration File to store the credentials to the Server. To make sure if what you are saying 9is what am assuming. can you please send us the error ?

Jon_Boy wrote: I think I found a way to accomplish what I need Care to share? It might help someone else.

NP

Does anyone know how to execute a parameterized stored procedure that returns a recordset using ADO .NET? I noticed neither direct Parameter members on the DataAdapter nor Fill members on a db_Command. My workaround has been to use an Adapter to execute a query such as "EXECUTE Procedure 1, 2, 3". I would prefer not to execute a reader. --1st method System::Data::OleDb::OleDbCommand ^db_Command=gcnew...

Generally speaking, each data item (that is not a primary or foreign key) should only appear in one table, otherwise you will have referential integrity issues. Course table - looks fine. Instructor table - looks fine. Class table - Probably doesn't need a composite key between ClassCode and CourseCode, however I assume InstrName is the Instructor name - this doesn't need to be in there, as it's in the Instructor Table....

Thank you, I also found this example, but the examples assume, that an Excel file already exists. But I remember, 5 years ago, I could generate a new file with the sql-sting above (within VB6) without an additional action. Why can't I do that today - or how can I do that today ? Tnx for your time Frank