|
If you are talking about short circuiting in boolean conditions, then the answer is no.
Fields will not necessarily be updated in the order they are presented. Some fields require more work in an update, and (in a multi-processor environment) the operations to do this can happen alongside other parts of the update.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
wow, no short circuting of booleans, eh? So (X > 0 AND Y < 3), if x is -1 it will still evaluate y < 3? That's crazy!
On doing the updates, I kind of figured that. I'm not too familar on what goes on behind the scenes like if it locks the whole record or locks at the field level.
I can work with both these issues and will be good to know for the future.
Do you know if this is any different in SQL Server 2005? I know my company will be upgrading here sometime in the future ( I have seen the install discs with my own eyes). I just hope that whatever I have done will be easy to port over. 
Best Regards,
Keith
|
|
|
|
|
|
Very interesting. Well, that throws the conventional wisdom out of the window.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
|
|
I can't understand my friend what do you mean ??
jooooo
|
|
|
|
|
In your OP, you stated that you got a message and then just showed Smileys. I was trying to ask what message you actually got.
BTW - it's not a good idea to use the SA account to connect to SQL Server. This is a full privilege account that should not be used for general purpose access. You should create an account that just does what you need it to do and lower the attack surface of your application.
If you keep using the SA account, there is every chance that somebody could get access to your database and do things to it that you really don't want it to do.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
thanks my friend for your reply >>
the message is >>
Could not load file or Assembly ( ADODB, Version=7.0.3300.0, Culture=neutral , Publickey token = bo3f5711d5.a3a) or one of its dependencies . The system can nptfind the file specified
I hope if you can aid me >>
jooooo
|
|
|
|
|
OK - that's kind of weird because the Sql classes don't use ADODB. They integrate with SQL Server at a much lower level.
Anyway, this section on the MSDN forums might be helpful: Clickety[^]
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Thanks my friend for your interest ..
the problem is solved ,,,
but another problem appear ...
the new message is :
Can not logon to ServerComputerName
so sorry my friend to make you tire ,,
but my work is stopped for this problem
jooooo
|
|
|
|
|
I want to use the following update command multiple times:
command.CommandText = ("UPDATE EndOfMonth SET [Rented Depreciation] = @RD, [Unrented Depreciation] = @UD,");
command.CommandText += ("CashSales = @CS, BuyOuts = @BO, ChargeOffs = @CO WHERE StoreNumber = @SN");
command.Parameters.Add("@RD",OleDbType.Numeric);
command.Parameters.Add("@UD",OleDbType.Numeric);
command.Parameters.Add("@CS",OleDbType.Numeric);
command.Parameters.Add("@BO",OleDbType.Numeric);
command.Parameters.Add("@CO",OleDbType.Numeric);
command.Parameters.Add("@SN",OleDbType.VarChar);
How do I assign values to this command after defining it?
I can assign values to it at this time, but if I call it again, I will be adding more and more parameters, correct?
I am google searching the earth and this site, but only had 3 returns for OleDbCommand UPDATE.
Thanx in advance
Jude
|
|
|
|
|
command.Parameters.Item("@SN").Value = "MyNewValue"
|
|
|
|
|
|
Ok now I am stumped about something. Here is the parameter:
command.Parameters.Add("@RD",OleDbType.Decimal);
Here is the assignment:
command.Parameters["@RD"].Value = decTotDepr; (holds a decimal value of 40873.77)
The field is defined as Number, Field Size: Decimal, Format: General Number, Precision: 18(left at default), Scale: 0, Decimal Places:2 (in access).
When writing to the database, it stores only the integer part(40873).
Do I need to add more information to the definition of the parameter?
Jude
|
|
|
|
|
After scouring the earth for information on scale and finding nothing, I found ONE line defining what scale was in my 900+ page SQL 2000 book and nothing in my 400+ page access book. Just something little I guess you forget when you don't program everyday!
Jude
|
|
|
|
|
Hi Everyone.
I am trying to delete data from datagrid
here is my code:
DataTable tbl = new DataTable("timesheet");
tbl = ds.Tables[0];
int i = this.iRowIndex
tbl.Rows[i].Delete();
this.daDisplay.Update(tbl);
I am getting an exception: "there is no row at position 0",whereas there is data in the database...what can be the proble,I can't seem to figure it out.
pls help..
|
|
|
|
|
Well, you create the table as a standalone datatable, and then you point it to ds.Tables[0]. If you haven't actually read anything from the database then this will be the problem.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Hi Everyone.
I am trying to delete data from datagrid
|
|
|
|
|
SQL Server usage is ...
ALTER TABLE tablename ALTER COLUMN columnname datatype
also the new column added to the table will have NULL initially.
however after updating all existing NULLs with some data, the column can be changed to NOT NULL
|
|
|
|
|
thanks for the reply.
i have one more question to ask.
can i drop the primary key constraint on a column without actually dropping the column??
|
|
|
|
|
Yes.
ALTER TABLE tablename DROP CONSTRAINT constraintname
to know the Primayr key constraint name
SP_HELP tablename
|
|
|
|
|
thanks man ur the best
|
|
|
|
|
I have written the following code but it doesn't seem to be working. I think it's pretty clear what it is supopposed to achieve. I believe the error to be purely syntax. Any ideas?
ALTER PROCEDURE [dbo].[SP_PermutationsUnconfiguredSelect] <br />
-- Add the parameters for the stored procedure here<br />
@UserID nvarchar(5),<br />
@Type nvarchar(15),<br />
@Credit nvarchar(15)<br />
AS<br />
DECLARE @Query varchar(500)<br />
DECLARE @Where varchar(500)<br />
<br />
SET @Where = ''<br />
SET @Query = 'SELECT PermID, ([Type] + " with "+ Credit + " credit for " + Purpose)As Permutation<br />
FROM Permutations<br />
WHERE PermID NOT IN (SELECT PermutationID FROM Products WHERE UserID = ' + @UserID + ')'<br />
<br />
BEGIN<br />
IF @Credit = 'Both'<br />
SET @Where = 'AND [Type] = ' + @Type<br />
ELSE<br />
SET @Where = 'AND [Type] = ' + @Type + ' AND Credit =' + @Credit<br />
<br />
EXEC(@Query + @Where )
|
|
|
|
|
You can put in a PRINT statement before (or temporarily in place of) the EXEC to see what is actually being generated
PRINT(@Query)
PRINT(@Where)
I think that probably the " is what is causing confusion. When expanded out the " is being seen as defining a column name. You can use [ColumnName] and "ColumnName" to define explicit column names, especially ones that contain odd characters or spaces.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
