Database

Thanks a lot dear friends for your valuable time. I have installed SQL EXPRESS 2008 but it was not EXPRESS R2 version thats why its creating problem. I came to know that thing when i was changing the initial size of database to 5500 MB. Thankx.

shiva.kore wrote: lan1 marks What does this represent in your ideas. Do you want a count of all students who scored < 35 in EVERY subject. This is quite a bit more complex and requires more knowledge of your data. Basically get a distinct list of all student/scores > 35 then get a list of all student/scores who are NOT IN the > 35 list. Never underestimate the power of human stupidity RAH

Not a database related question, more a C# question. What you need to do is Handle the TextChanged or ValueChanged event of the ComboBox. In the event handler, populate the ListBox with the required data from your database etc. Steve Jowett ------------------------- Real Programmers don't need comments -- the code is obvious.

DECLARE @rtDayofWeek VARCHAR(10) DECLARE @dtDate datetime DECLARE @endDate datetime SET @dtDate = '8/25/2010' SET @endDate = '8/27/2010' WHILE @dtDate <= @endDate BEGIN SELECT @rtDayofWeek = CASE DATEPART(weekday,@dtDate) WHEN 1 THEN 'Sunday' WHEN 2 THEN 'Monday' WHEN 3 THEN 'Tuesday' WHEN 4 THEN 'Wednesday' WHEN 5 THEN 'Thursday' WHEN 6 THEN 'Friday' WHEN 7 THEN 'Saturday' END PRINT @rtDayofWeek SET @dtDate = DATEADD(Day,1,@dtDate) END Hope this helps buddy :D None :D

I think if you install MDAC_TYP 2.8 or earlier may solve your issue.

It is not the only one[^]... :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Thanks bhiller, I'm downloading it. but it seems to be a huge file.

OK. thank you.

:~ As it turns out, in my RecordSet class m_bCheckCacheForDirtyFields was set to FALSE. This turns off automatic double buffering and means you have to manually set fields dirty, otherwise they won't save when you call Update. Blah. Flip the switch and it works...

If it's not possible to use SQL Server as others have suggested, you can always encrypt data that's being written into the DB, where the encryption library will be in your application. But it's not fool proof, and it'll mightily slow down all data access. SG Aham Brahmasmi!

Nikhil Bhivgade wrote: A/101/2010 That looks like three values to me. How about splitting them over different columns? That way you could easily SORT the values any way you'd want :) I are Troll :suss:

CDO will work if you're only ever sending to a single address and you have your anti-virus/firewall configured to allow emails to be sent out originating from your computer; and if you allow spam from your origin address on the destination account. If you're looking to email end users with a non-static address, I recommend looking into other solutions.

LOL! I've been saying the same thing for three years. Either I'll convince someone that we need to write our own application to replace this one, or hope the vendor moves away from this model.

I hope you did not wait for an answer - a simple search [^]would have given you many answers Never underestimate the power of human stupidity RAH

bulkCopy.DestinationTableName = strTableName is sufficient, de database is in the sqlConnectionString

Restore or attach the 2005 database to your sql2008 server and change the compatibility level. Just what are you expecting to change when you move to 2008? Never underestimate the power of human stupidity RAH

Doesn't ring a bell, I'm afraid. Still, executing both commands one after another should do the trick - without a need to combine them. @@IDENTITY should hold it's value until the next INSERT-statement is issued. I are Troll :suss:

The Office Suite is meant for interactive use, and will pop up all kinds of dialogs when it sees fit. AFAIK there isn't much you can do about that. Of course you don't need the Access application, you could create your own app (with GUI and business logic) and use OLEDB and an access database file as the data store. That won't pop up anything you didn't design. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

This is because the @@ values get reset when an action (print) executes.

Yes, that's the one to get.