dinoboy

The page can only contain one visible server-side form. So if you can put the Google form outside the main page form, then it should be working fine. Or you may add the onclick handler to the submit button to submit the specific form. In that case you should also add name or id attribute to that Google form. If that don't work, change that input type to 'button' instead of submit. <form name="googleForm" method="get" action="Search.aspx" target="_top"> ... <input type="submit" name="sa" value="Google Search" id="sbb" OnClick="document.forms['googleForm'].submit();"></input> ... Give it a try, it should work :)

Depends what you want to do with that count next, you may also store the value in viewstate instead of session.

Yes, this can be done with COUNT() function and GROUP BY statement SELECT COUNT(name) AS count, name FROM table GROUP BY name Where 'table' is name of the table and column 'name' is the name of the column you use.

I had 512mb of ram and yeah, it's very slow. After I added extra 1gb of ram the performance boost was huge. But still there seems to be some problems with VS2005. After closing the program, sometimes the devenv.exe instance just keeps running. Have someone encountered the same problem?

If you don't want to use the autogenerated columns then you can set the AutoGeneratedColumns property to false. To bind the ComboBox column, you set it's DataSourceID (you may use DataSource property too, if you want). For example something like that. YourComboBoxColumn.DataSource = db.GetDataSet("your_second_query").Tables(0)

Do you want to update the existing row or add a new row? If you are trying to update, then you should use Dim dr As DataRow = dtCustomers.Rows[dtCustomers.EditItemIndex] which returns the row which you are editing Right now you are using Dim dr As DataRow = dtCustomers.NewRow which returns the newly added row and of course in case of update, cells have no values.

If you manually create the DataGridView columns, then you can add a ComboBoxColumn and bind it to that query.

If you want use both .NET 1.1 & 2.0 applications, you must have both versions installed. You then create a virtual directory under IIS (or with VS2005 you can use it's built-in server) and choose the appropriate .NET version. FYI you can't use VS2003 and VS2005 on the same project. Once VS2005 converts the project file to the new format, it cannot be used with VS2003.

If you can/may change the database and the FK, then you should set the FK delete rule to cascade. Cascade means that when you want to delete/update the row in primary table then the rows are updated/deleted from the tables with foreign key too. In your case you should then delete only from table GridGroups and matched rows from GridTrans would deleted automaticly. Other option, if you can't change the FK rule... You don't say in your error with which table the integrity constraint violation appears? I mean there may be other tables with FK's to GridGroups table. If so, then you can't delete from GridGroups unless you first delete all matching rows from all other tables with relations.

In addition, some browsers or other settings may disallow HTTP refferes. So even when the page shouldn't be accessible without a reffere, you should check if the refferer is set. I just had the same problem, because my Firefox didn't set refferer.

Yes you can.

But if you call just ? public MyAbstract() { }

Finally I found what was wrong.... The problem wasn't related with the threading. It was caused by the lenght of the progress bar and it's values. When I assigned the value to 0, then it still showed one bar.

Actually I don't start any new threads. Simply Asynchronous request is made and while it is making the request I want to display to the user a progress bar. And for updating it, I use System.Timers.Timer class, whcich automatically starts in a new thread.

I am developing an application which makes the search request via the web service. Meanwhile the progress bar control is displayed to the user. Now, I am using a timer to update the progress bar. As far as I know, the System.Timer should start in the new thread... and here I am having a problem... Start the timer: this.timer.Interval = 100; this.timer.Elapsed += new System.Timers.ElapsedEventHandler(this.cbProgressBar_update); this.timer.Start(); And when timer elapsed, I want to update my progress bar. The progress bar owner is the main UI thread, but the event is raised in the timer thread. So I can't call in cpProgressBar_update method just this.progressBar.PerformStep(). Am I right? Should I use Invoke() methods in the raised event? I have tried different solutions I have thought about, but the results weren't what I had expected...